CN106874384B - Heterogeneous address standard conversion and matching method - Google Patents
Heterogeneous address standard conversion and matching method Download PDFInfo
- Publication number
- CN106874384B CN106874384B CN201710016546.XA CN201710016546A CN106874384B CN 106874384 B CN106874384 B CN 106874384B CN 201710016546 A CN201710016546 A CN 201710016546A CN 106874384 B CN106874384 B CN 106874384B
- Authority
- CN
- China
- Prior art keywords
- address
- matching
- information
- administrative
- result
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Remote Sensing (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A heterogeneous address standard conversion and matching method comprises forward matching, reverse matching and home matching, wherein the forward matching comprises information point matching and detailed address matching, and address information is standardized by combining a method of administrative region completion and standardized field processing. The invention adopts a multi-stage matching method and sets a return flow, effectively distinguishes the results of single correlation and multiple correlations, has higher fault-tolerant rate, can adapt to the requirements of different industries on the address, and has high matching accuracy.
Description
Technical Field
The invention belongs to the field of geographic information, and relates to a heterogeneous address standard conversion and matching method.
Background
With the development of big data, the address cloud platform is an external application and service platform based on a space standard address, real-time extraction, cleaning, matching and map loading of business data are achieved, the system achieves full map loading of the business data through forward and reverse matching, thematic mapping and publishing are carried out on the mapped business data, personalized requirements of various industries on maps are met, and exclusive maps of various industries are created. Address matching is the process of establishing correspondence between textual descriptive addresses and the spatial geographical location coordinates. The address matching service looks up matching objects for addresses according to specific steps. Firstly, standardizing an address; then the server searches the address matching reference data and searches a potential position; each candidate location is assigned a score based on its proximity to the address, and the address is finally matched with the highest score.
CN 105005577 discloses an address matching method, which adopts a layered progressive matching method, specifically comprising four steps of quick matching, longitude and latitude matching, fuzzy matching and manual judgment, wherein the quick matching is used for accurately matching a high-quality target address, and a chain type supplement mechanism is used for properly supplementing matching; the longitude and latitude matching is carried out on the target address and the adjacent cell thereof according to the longitude and latitude information provided by the map service provider; fuzzy matching is carried out on the target address and the similar cell by using a fuzzy index; and a manual judgment mechanism is used for checking and checking the matching result. The invention also comprises an address word segmentation technology and a confidence index mechanism of address matching accuracy. Although the invention applies the problem of compound application of multiple address matching technology, the address is standardized, so that the invention is difficult to adapt to the requirements of different fields on the address.
Disclosure of Invention
The invention provides a heterogeneous address standard conversion and matching method, which aims to overcome the defects of difficult address standardization, low adaptability and low accuracy.
In order to achieve the above object, the present invention provides a heterogeneous address standard conversion and matching method, which comprises the following steps:
step 1: and (3) verifying the data validity: if the data is legal, executing the step S2, otherwise, directly throwing the exception and ending the execution;
step 2: judging the forward matching of the data, if so, obtaining a matched administrative division information identifier, and performing forward matching; if the data does not meet the forward matching, performing reverse matching;
and step 3: judging whether the result of the forward matching or the reverse matching in the step 2 is empty, if so, throwing an exception, and ending the execution; if the matching result is not null, obtaining matching result information data;
and 4, step 4: judging whether the administrative districts are matched or not according to the matching result information data in the step 3, if so, performing attribution matching and returning a result; otherwise, directly returning the result and finishing the execution.
Preferably, the specific steps of the forward matching are sequentially as follows:
s11, verifying the validity of the data according to the incoming data detail address information and the information of province, city, district and county, and if the data are combined, performing the step S12; if the data is illegal, directly throwing the exception, and ending the execution;
s12: dividing data into information data of other conditions such as information points, detailed address information data, province, city, district and county and the like; if the data is information data of province, city, district and county, performing administrative district completion and standardized field processing;
s13: judging whether the incoming data has no information point and no detailed address at the same time according to the step S12; if the incoming data has no information point and detailed address at the same time, executing the processing without detailed address and information point and returning the result; if the incoming data is the information point or the detailed address information, the information point matching or the detailed address matching is executed correspondingly.
Further, the steps of completion of the administrative region and processing of the standardized fields are as follows in sequence:
s121, splicing and assembling the incoming data to inquire addresses, wherein the addresses comprise province, city, district and county, villages and towns, residence committee and street lane;
s122, splitting the spliced addresses to obtain corresponding phrases;
s123, solving the conflict problem of the administrative divisions by taking the selected administrative divisions as a standard;
and S124, executing Solr address query, completing province, city, district and county fields, and obtaining a standardized phrase list after word segmentation.
Further, the step of completing and processing standardized fields of the administrative region further comprises re-standardizing addresses, which in turn are:
firstly, acquiring a standard address SolrBean;
standardizing administrative division addresses according to the phrase types, and returning to a standard address Solr object; if the Solr objects do not exist or exist in multiple numbers, inquiring the address of the previous stage, and if the Solr objects do not exist or exist in multiple numbers, continuously inquiring the address of the previous stage until the Solr objects are unique;
finally, judging whether the standard address exists or not and whether the standard address matches the nearest address or not, if so, matching the nearest address, and specially matching doorplates, units and rooms; if no recent address exists, the obtained standard value SolrBean is returned.
Preferably, the specific steps of step S13 without detailed address and information point are:
s131, standardizing the address again, and setting and returning a minimum level administrative region standard address;
s132, judging whether the returned standard address exists: if yes, setting a matching rate score, and then acquiring standard address information of the minimum-level administrative division to obtain final standard address information; if not, throwing out exception processing and finishing execution.
Preferably, the information point matching step sequentially comprises:
firstly, judging whether a standard address of an information point exists, if so, executing standard address information according to the information point, and if not, executing detailed address matching;
then, setting administrative division codes and names according to the obtained standard address information;
and finally, carrying out matching rate conversion to obtain the final returned result object data.
The step of address detail matching is as follows in sequence:
firstly, solving the problem of administrative division conflict;
completing the phrase list according to the address extension object;
secondly, re-standardizing the address, and setting and returning a minimum-level administrative division standard address;
and then judging whether the returned standard address exists, if the standard address of the administrative division is not found, throwing exception handling, and if the standard address exists, judging whether the longitude and latitude coordinates are all zero: if the longitude and latitude coordinates are zero, the upper-level standard address is found up until standard address data are obtained; if the longitude and latitude coordinates are not zero, standard address data are obtained;
judging whether the standard address data only needs to be matched with one record, if so, setting a matching rate, and setting a return result object to obtain matching result object data; if one record does not need to be matched, executing solr query, matching a plurality of results, and obtaining matched result object data;
and finally, setting the administrative division codes and names according to the matching result object data, and returning the result.
Preferably, the step of reverse matching is:
firstly, inputting longitude and latitude XY coordinates and searching radius;
searching the information point with the nearest distance according to the longitude and latitude XY coordinates and the searching radius;
judging whether an information point exists in the final search radius, if so, returning the address information of the information point closest to the final search radius, and then returning the result; if not, the result object with the matching state being not matched to the proper address is set to return the result.
Preferably, the specific steps of attribution matching are as follows in sequence:
the method comprises the steps that related information of an address fragment object is transmitted, wherein the related information comprises administrative division codes, administrative district codes and longitude and latitude;
judging whether attribution matching is needed, if not, setting a result returning object and returning a result, if so, judging whether a management jurisdiction code exists: if the administrative district code exists, searching administrative district related information according to the administrative district code, setting a return result object and returning a result, and if the administrative district information is not searched, inquiring the administrative district information.
Further, the concrete steps of managing the query of the jurisdiction are as follows:
firstly, an administrative code list is assembled according to an address fragment object, and whether the size of the administrative code list is larger than 1 is judged according to the arrangement sequence of the administrative partitions from small to large: if the political region code list is not more than 1, performing solr space query according to the transmitted longitude and latitude coordinates to obtain matched minimum management region information, setting the obtained minimum management region information as a return result object and returning a result; if the administrative division code list is larger than 1, executing 'taking the 1 st according to the incoming administrative coding list and inquiring the association relation of the administrative district';
then judging whether the root management jurisdiction association relation query has a result: if no result is obtained, executing the step of removing the current administrative division code from the administrative division code column to obtain a new administrative division list, and then returning to the step of judging whether the size of the administrative division code list is larger than 1; if the query has a result, judging whether the query is unique;
if the query result is unique, acquiring management jurisdiction information, setting the management jurisdiction information as a returned result object and returning a result; if the query result is not unique, judging whether the administrative district association relationship is at the street lane level: if the number is the street level, successively judging the administrative codes downwards until the minimum administrative district information is matched, setting the obtained minimum administrative district information as a return result object and returning a result; and if the administrative division code is not at the street lane level, returning to the step of removing the current administrative division code from the administrative division code column.
The invention has the beneficial effects that:
1. service data (database, table or other form data) is conveniently configured through a tool, and matching items and matching output items are specified;
2. the forward and reverse matching of the address can be realized through the service, and the matching result is evaluated; home matching may improve the accuracy of conventional forward matching.
3. The administrative division completion and standardized field processing can meet the requirements of different fields on addresses, improve the adaptability of the addresses and output matching results into thematic maps; .
4. The multi-stage matching method and the return flow are set, the results of single correlation and multiple correlations are effectively distinguished, the fault tolerance rate is higher, and the matching accuracy is improved.
Drawings
FIG. 1 is a general flow diagram of the address matching method of the present invention;
FIG. 2 is a flow chart of a forward matching method of the present invention;
FIG. 3 is a flow chart of administrative region completion and standardized field processing of the present invention;
FIG. 4 is a flow chart of the present invention for re-normalizing addresses;
FIG. 5 is a flow chart of the present invention without detailing addresses and information points;
FIG. 6 is a flow chart of information point matching of the present invention;
FIG. 7 is a flow chart of the present invention detailing address matching;
FIG. 8 is a flow chart of the reverse matching of the present invention;
FIG. 9 is a flow chart of home matching of the present invention.
Detailed Description
In order to better understand the technical solution proposed by the present invention, the following further explains the present invention with reference to the drawings and specific embodiments.
As shown in fig. 1, a heterogeneous address standard conversion and matching method is characterized by sequentially comprising the following steps:
step 1: verifying the data validity, namely verifying whether the incoming information does not contain address information, if so, executing the step S2, otherwise, directly throwing out the exception and ending the execution;
step 2: judging the forward matching of the data, if so, obtaining a matched administrative division information identifier, and performing forward matching; if the data does not meet the forward matching, performing reverse matching;
and step 3: judging whether the result of the forward matching or the direction matching in the step S2 is empty, if so, throwing out an exception, and ending the execution; if the matching result is not null, obtaining matching result information data;
and 4, step 4: judging whether the administrative districts are matched or not according to the matching result information data in the S3, and if so, performing attribution matching and returning a result; otherwise, directly returning the result and finishing the execution.
1. Forward matching
As shown in fig. 2, the specific steps of the forward matching are in sequence:
s11, verifying the legality of the data according to the incoming data detailed address information and other condition information such as province, city, district and county, and if the data are combined, performing the step S12; if the data is illegal, directly throwing the exception, and ending the execution;
s12: dividing data into information data of other conditions such as information points, detailed address information data, province, city, district and county and the like; if the data is information data of other conditions such as province, city, district and county, performing administrative region completion and standardized field processing;
s13: judging whether the incoming data has no information point and no detailed address at the same time according to the step 12; if the incoming data has no information point and detailed address at the same time, executing the processing without detailed address and information point and returning the result; if the incoming data is the information point or the detailed address information, the information point matching or the detailed address matching is executed correspondingly.
1.1 administrative region completion and standardized field processing
As shown in fig. 3, the steps of completion of administrative regions and processing of standardized fields are as follows:
s121, splicing and assembling the incoming data to inquire addresses, wherein the addresses comprise province, city, district and county, villages and towns, residence committee and street lane;
s122, splitting the spliced addresses to obtain corresponding phrases;
s123, solving the conflict problem of the administrative divisions by taking the selected administrative divisions as a standard;
and S124, executing Solr address query, completing province, city, district and county fields, and obtaining a standardized phrase list after word segmentation.
1.2 renormalizing addresses
As shown in fig. 4, the step of re-normalizing the address is:
firstly, acquiring a standard address SolrBean;
standardizing administrative division addresses according to the phrase types, and returning to a standard address Solr object; if the Solr objects do not exist or exist in multiple numbers, inquiring the address of the previous stage, and if the Solr objects do not exist or exist in multiple numbers, continuously inquiring the address of the previous stage until the Solr objects are unique; finally, judging whether the standard address exists or not and whether the standard address matches the nearest address or not, if so, matching the nearest address, and specially matching doorplates, units and rooms; if no recent address exists, the obtained standard value SolrBean is returned.
1.3 having no detailed address and information point
As shown in fig. 5, the specific steps without detailed address and information point are:
s131, standardizing the address again, and setting and returning a minimum level administrative region standard address;
s132, judging whether the returned standard address exists: if yes, setting a matching rate score, and then acquiring standard address information of the minimum-level administrative division to obtain final standard address information; if not, throwing out exception processing and finishing execution.
1.4 information point matching
As shown in fig. 6, the specific steps of information point matching are as follows:
firstly, judging whether a standard address of an information point exists, if so, executing standard address information according to the information point, and if not, executing detailed address matching;
then, setting administrative division codes and names according to the obtained standard address information;
and finally, carrying out matching rate conversion to obtain the final returned result object data.
1.5 address matching
As shown in fig. 7, the steps of address matching in detail are:
firstly, solving the problem of administrative division conflict; completing the phrase list according to the address extension object; secondly, re-standardizing the address, and setting and returning a minimum-level administrative division standard address; and then judging whether the returned standard address exists, if the standard address of the administrative division is not found, throwing exception handling, and if the standard address exists, judging whether the longitude and latitude coordinates are all zero: if the longitude and latitude coordinates are zero, the upper-level standard address is found up until standard address data are obtained; if the longitude and latitude coordinates are not zero, standard address data are obtained;
judging whether the standard address data only needs to be matched with one record, if so, setting a matching rate, and setting a return result object to obtain matching result object data; if one record does not need to be matched, executing solr query, matching a plurality of results, and obtaining matched result object data;
and finally, setting the administrative division codes and names according to the matching result object data, and returning the result.
2. Reverse matching:
as shown in fig. 8, the specific steps of reverse matching are:
firstly, inputting longitude and latitude XY coordinates and searching radius;
searching the information point with the nearest distance; and searching the nearest information point in the buffer area by a solr space query method. And secondly, searching whether an information point exists in the radius, if so, returning the address information of the information point closest to the information point and returning a result, and if not, setting the obtained matching state as a result object which is not matched with the proper address and then returning the result.
3. Attribution matching
As shown in fig. 9, the specific steps of attribution matching are as follows:
the method comprises the steps that related information of an address fragment object is transmitted, wherein the related information comprises administrative division codes, administrative district codes and longitude and latitude;
judging whether attribution matching is needed, if not, setting a result returning object and returning a result, if so, judging whether a management jurisdiction code exists: if the administrative district code exists, searching administrative district related information according to the administrative district code, setting a return result object and returning a result, and if the administrative district information is not searched, inquiring the administrative district information.
3.1 managing jurisdictional information query
The method comprises the following specific steps:
firstly, an administrative code list is assembled according to an address fragment object, and whether the size of the administrative code list is larger than 1 is judged according to the arrangement sequence of the administrative partitions from small to large: if the political region code list is not more than 1, performing solr space query according to the transmitted longitude and latitude coordinates to obtain matched minimum management region information, setting the obtained minimum management region information as a return result object and returning a result; if the administrative division code list is larger than 1, executing 'taking the 1 st according to the incoming administrative coding list and inquiring the association relation of the administrative district';
then judging whether the root management jurisdiction association relation query has a result: if no result is obtained, executing the step of removing the current administrative division code from the administrative division code column to obtain a new administrative division list, and then returning to the step of judging whether the size of the administrative division code list is larger than 1; if the query has a result, judging whether the query is unique;
if the query result is unique, acquiring management jurisdiction information, setting the management jurisdiction information as a returned result object and returning a result; if the query result is not unique, judging whether the administrative district association relationship is at the street lane level: if the number is the street level, successively judging the administrative codes downwards until the minimum administrative district information is matched, setting the obtained minimum administrative district information as a return result object and returning a result; and if the administrative division code is not at the street lane level, returning to the step of removing the current administrative division code from the administrative division code column.
Adaptation and modification of the relevant modules and software architectures of the above-described embodiments may also be made by those skilled in the art, given the benefit of the teachings and teachings of the above description. Therefore, the present invention is not limited to the specific embodiments disclosed and described above, and some modifications and variations of the present invention should fall within the scope of the claims of the present invention. Furthermore, although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Claims (7)
1. A heterogeneous address standard conversion and matching method is characterized by sequentially comprising the following steps:
step 1: and (3) verifying the data validity: if the data is legal, executing the step 2, otherwise, directly throwing the exception and finishing the execution;
step 2: judging whether the data meet forward matching, if so, obtaining a matched administrative division information identifier, and performing forward matching; if the data does not meet the forward matching, performing reverse matching;
and step 3: judging whether the result of the forward matching or the reverse matching in the step 2 is empty, if so, throwing an exception, and ending the execution; if the matching result is not null, obtaining matching result information data;
and 4, step 4: judging whether the administrative districts are matched or not according to the matching result information data in the step 3, if so, performing attribution matching and returning a result; otherwise, directly returning the result and finishing the execution;
the specific steps of the forward matching are as follows in sequence:
s11, verifying the validity of the data according to the incoming data detail address information and the information of province, city, district and county, and if the data are combined, performing the step S12; if the data is illegal, directly throwing the exception, and ending the execution;
s12: dividing data into information points, detailed address information data and information data of province, city, district and county; if the data is information data of province, city, district and county, performing administrative district completion and standardized field processing;
s13: judging whether the incoming data has no information point and no detailed address at the same time according to the step S12; if the incoming data has no information point and detailed address at the same time, executing the processing without detailed address and information point and returning the result; if the incoming data is information point or detailed address information, correspondingly executing information point matching or detailed address matching;
the reverse matching step comprises:
firstly, inputting longitude and latitude XY coordinates and searching radius;
searching the information point with the nearest distance according to the longitude and latitude XY coordinates and the searching radius;
judging whether an information point exists in the final search radius, if so, returning the address information of the information point closest to the final search radius, and then returning the result; if not, setting the obtained matching state as a result object which is not matched with the proper address and then returning a result;
the specific steps of attribution matching are as follows in sequence:
the method comprises the steps that related information of an address fragment object is transmitted, wherein the related information comprises administrative division codes, administrative district codes and longitude and latitude; judging whether attribution matching is needed, if not, setting a result returning object and returning a result, if so, judging whether a management jurisdiction code exists: if the administrative district code exists, searching administrative district related information according to the administrative district code, setting a return result object and returning a result, and if the administrative district information is not searched, inquiring the administrative district information.
2. The method as claimed in claim 1, wherein the steps of completing and processing standardized fields of the administrative region are as follows:
s121, splicing and assembling the incoming data to inquire addresses, wherein the addresses comprise province, city, district and county, villages and towns, residence committee and street lane;
s122, splitting the spliced addresses to obtain corresponding phrases;
s123, solving the conflict problem of the administrative divisions by taking the selected administrative divisions as a standard;
and S124, executing Solr address query, completing province, city, district and county fields, and obtaining a standardized phrase list after word segmentation.
3. The method as claimed in claim 2, wherein the step of completing and processing standardized fields of the administrative area further comprises re-standardizing addresses in the order of:
firstly, acquiring a standard address SolrBean;
standardizing administrative division addresses according to the phrase types, and returning to a standard address Solr object; if the Solr objects do not exist or exist in multiple numbers, inquiring the address of the previous stage, and if the Solr objects do not exist or exist in multiple numbers, continuously inquiring the address of the previous stage until the Solr objects are unique;
finally, judging whether the standard address exists or not and whether the standard address matches the nearest address or not, if so, matching the nearest address, and specially matching doorplates, units and rooms; if no recent address exists, the obtained standard value SolrBean is returned.
4. The method as claimed in claim 1 or 3, wherein the step S13 without detailed address and information point comprises the following steps:
s131, standardizing the address again, and setting and returning a minimum level administrative region standard address;
s132, judging whether the returned standard address exists: if yes, setting a matching rate score, and then acquiring standard address information of the minimum-level administrative division to obtain final standard address information; if not, throwing out exception processing and finishing execution.
5. The method as claimed in claim 2, wherein the step of matching the information points comprises:
firstly, judging whether a standard address of an information point exists, if so, executing standard address information according to the information point, and if not, executing detailed address matching;
then, setting administrative division codes and names according to the obtained standard address information;
and finally, carrying out matching rate conversion to obtain the final returned result object data.
6. The method as claimed in claim 1 or 3, wherein the step of matching addresses in detail comprises:
firstly, solving the problem of administrative division conflict;
completing the phrase list according to the address extension object;
secondly, re-standardizing the address, and setting and returning a minimum-level administrative division standard address;
and then judging whether the returned standard address exists, if the standard address of the administrative division is not found, throwing exception handling, and if the standard address exists, judging whether the longitude and latitude coordinates are all zero: if the longitude and latitude coordinates are zero, the upper-level standard address is found up until standard address data are obtained; if the longitude and latitude coordinates are not zero, standard address data are obtained;
judging whether the standard address data only needs to be matched with one record, if so, setting a matching rate, and setting a return result object to obtain matching result object data; if one record does not need to be matched, executing solr query, matching a plurality of results, and obtaining matched result object data;
and finally, setting the administrative division codes and names according to the matching result object data, and returning the result.
7. The method for converting and matching heterogeneous address standards according to claim 1, wherein the specific steps for managing the query of the jurisdiction are as follows:
firstly, an administrative code list is assembled according to an address fragment object, and whether the size of the administrative code list is larger than 1 is judged according to the arrangement sequence of the administrative partitions from small to large: if the political region code list is not more than 1, performing solr space query according to the transmitted longitude and latitude coordinates to obtain matched minimum management region information, setting the obtained minimum management region information as a return result object and returning a result; if the administrative division code list is larger than 1, executing 'taking the 1 st according to the incoming administrative coding list and inquiring the association relation of the administrative district';
then judging whether the management jurisdiction association relation query has a result: if no result is obtained, executing the step of removing the current administrative division code from the administrative division code column to obtain a new administrative division list, and then returning to the step of judging whether the size of the administrative division code list is larger than 1; if the query has a result, judging whether the query is unique;
if the query result is unique, acquiring management jurisdiction information, setting the management jurisdiction information as a returned result object and returning a result; if the query result is not unique, judging whether the administrative district association relationship is at the street lane level: if the number is the street level, successively judging the administrative codes downwards until the minimum administrative district information is matched, setting the obtained minimum administrative district information as a return result object and returning a result; and if the administrative division code is not at the street lane level, returning to the step of removing the current administrative division code from the administrative division code column.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710016546.XA CN106874384B (en) | 2017-01-10 | 2017-01-10 | Heterogeneous address standard conversion and matching method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710016546.XA CN106874384B (en) | 2017-01-10 | 2017-01-10 | Heterogeneous address standard conversion and matching method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106874384A CN106874384A (en) | 2017-06-20 |
| CN106874384B true CN106874384B (en) | 2020-12-04 |
Family
ID=59157332
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710016546.XA Active CN106874384B (en) | 2017-01-10 | 2017-01-10 | Heterogeneous address standard conversion and matching method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106874384B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107656913B (en) * | 2017-09-30 | 2021-03-23 | 百度在线网络技术（北京）有限公司 | Map interest point address extraction method, map interest point address extraction device, server and storage medium |
| CN110795512B (en) * | 2018-07-17 | 2023-08-01 | 中国移动通信集团重庆有限公司 | Address matching method, device, equipment and storage medium |
| CN110442617A (en) * | 2019-06-27 | 2019-11-12 | 华迪计算机集团有限公司 | A kind of method and system carrying out dynamic processing to statistical data based on administration cell |
| CN110442603B (en) * | 2019-07-03 | 2024-01-19 | 平安科技（深圳）有限公司 | Address matching method, device, computer equipment and storage medium |
| CN111159973B (en) * | 2019-12-13 | 2023-06-02 | 中关村科技软件股份有限公司 | Administrative division alignment and standardization method for Chinese addresses |
| CN111694823A (en) * | 2020-05-15 | 2020-09-22 | 平安科技（深圳）有限公司 | Organization standardization method and device, electronic equipment and storage medium |
| CN112115144A (en) * | 2020-09-15 | 2020-12-22 | 中电科华云信息技术有限公司 | Method for comparing address matching based on standard address matrix weighted mapping |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7376636B1 (en) * | 2002-06-07 | 2008-05-20 | Oracle International Corporation | Geocoding using a relational database |
| CN101719128A (en) * | 2009-12-31 | 2010-06-02 | 浙江工业大学 | Fuzzy matching-based Chinese geo-code determination method |
| CN102169498A (en) * | 2011-04-14 | 2011-08-31 | 中国测绘科学研究院 | Address model constructing method and address matching method and system |
| CN103530330A (en) * | 2013-09-29 | 2014-01-22 | 天泽信息产业股份有限公司 | Processing method of reverse geocoding processing system |
| CN106033460A (en) * | 2015-03-19 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Address data processing method and apparatus |
-
2017
- 2017-01-10 CN CN201710016546.XA patent/CN106874384B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7376636B1 (en) * | 2002-06-07 | 2008-05-20 | Oracle International Corporation | Geocoding using a relational database |
| CN101719128A (en) * | 2009-12-31 | 2010-06-02 | 浙江工业大学 | Fuzzy matching-based Chinese geo-code determination method |
| CN102169498A (en) * | 2011-04-14 | 2011-08-31 | 中国测绘科学研究院 | Address model constructing method and address matching method and system |
| CN103530330A (en) * | 2013-09-29 | 2014-01-22 | 天泽信息产业股份有限公司 | Processing method of reverse geocoding processing system |
| CN106033460A (en) * | 2015-03-19 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Address data processing method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106874384A (en) | 2017-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106874384B (en) | Heterogeneous address standard conversion and matching method | |
| CN104572645B (en) | Interest point data association method and device | |
| CN108628811B (en) | Address text matching method and device | |
| CN107145577A (en) | Address standardization method, device, storage medium and computer | |
| CN109359200A (en) | Place name address date intelligently parsing system | |
| CN106021336A (en) | A method for automatic administrative district division for mass address information | |
| CN103605752A (en) | Address matching method based on semantic recognition | |
| CN103714092A (en) | Geographic position searching method and geographic position searching device | |
| CN102693266A (en) | Method of searching a data base, navigation device and method of generating an index structure | |
| CN101996248B (en) | Address lookup method and device | |
| CN111931077A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112988715B (en) | Construction method of global network place name database based on open source mode | |
| KR20140097805A (en) | Coordinates (x, y) position value using a systematic block code generated and the address matching service using methods | |
| CN107203526A (en) | A kind of query string semantic requirement analysis method and device | |
| CN108062365B (en) | Method for improving address resolution accuracy | |
| CN112328910A (en) | Method and system covering AOI and POI standard address matching engine | |
| CN111538796A (en) | Address normalization processing method, device, equipment and storage medium | |
| CN106407221B (en) | Address data retrieval method and device | |
| CN111784239B (en) | Method and device for determining dispatch network point, electronic equipment and storage medium | |
| CN111966768B (en) | Address description method, address description device, electronic equipment and storage medium | |
| CN114722824A (en) | Address processing method and device, storage medium and electronic equipment | |
| TW202146850A (en) | Processing apparatus and method for determining road names | |
| CN106055635B (en) | Address information lookup method and device | |
| CN107220255B (en) | Address information processing method and device | |
| CN111475742A (en) | Address extraction method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 510000 no.502-518, North District, 5 / F, No.9, Jiangong Road, phase I Industrial Park, Tianhe Science and Technology Park, Tianhe District, Guangzhou City, Guangdong Province Applicant after: AEROSPACE JINGYI (GUANGDONG) INFORMATION TECHNOLOGY Co.,Ltd. Address before: 510000 Guangdong City, Guangzhou, Guangzhou Tianhe Software Park (Ke Yun Park) Road 9, 501 Applicant before: GUANGDONG FINEST PLANNING INFORMATION TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: No. 502-518, North Area, Floor 5, No. 9, Jiangong Road, Phase I Industrial Park, Tianhe Science Park, Tianhe District, Guangzhou, Guangdong 510000 Patentee after: Guangdong Jingyi Information Technology Co.,Ltd. Address before: No. 502-518, North Area, Floor 5, No. 9, Jiangong Road, Phase I Industrial Park, Tianhe Science Park, Tianhe District, Guangzhou, Guangdong 510000 Patentee before: AEROSPACE JINGYI (GUANGDONG) INFORMATION TECHNOLOGY Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |