[go: up one dir, main page]

US20150052152A1 - Location data integration and management - Google Patents

Location data integration and management Download PDF

Info

Publication number
US20150052152A1
US20150052152A1 US14/461,377 US201414461377A US2015052152A1 US 20150052152 A1 US20150052152 A1 US 20150052152A1 US 201414461377 A US201414461377 A US 201414461377A US 2015052152 A1 US2015052152 A1 US 2015052152A1
Authority
US
United States
Prior art keywords
data
primary
management
localization
geospatial coordinates
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.)
Abandoned
Application number
US14/461,377
Other languages
English (en)
Inventor
Ari KAUFMAN
Jake MEIER
Daniel Weiner
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ignite Local Search Solutions Inc
Original Assignee
Placeable LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Placeable LLC filed Critical Placeable LLC
Priority to PCT/US2014/051383 priority Critical patent/WO2015024007A2/fr
Priority to US14/461,377 priority patent/US20150052152A1/en
Publication of US20150052152A1 publication Critical patent/US20150052152A1/en
Assigned to PLACEABLE reassignment PLACEABLE ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KAUFMAN, Ari, MEIER, Jake, WEINER, DANIEL
Assigned to IGNITE LOCAL SEARCH SOLUTIONS, INC. reassignment IGNITE LOCAL SEARCH SOLUTIONS, INC. CERTIFICATE OF CONVERSION Assignors: PLACEABLE, LLC
Assigned to PLACEABLE, LLC reassignment PLACEABLE, LLC MEMBERSHIP INTEREST PURCHASE AGREEMENT CONFIRMING ASSIGNEE NAME Assignors: PLACEABLE
Priority to US16/689,955 priority patent/US11080312B2/en
Priority to US17/363,391 priority patent/US11580142B2/en
Priority to US18/154,628 priority patent/US12271405B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G06F17/30241—
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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

Definitions

  • Embodiments of the present invention relate, in general, to accessibility and usability of locational data and more particularly to systems and processes to increase the accuracy and reliably of locational data.
  • geocoding technology is in store/dealer locators. Businesses use geocoded data to ascertain proximity to potential customers, distance to suppliers and competitors, service areas and delivery routes. And consumers use geocoding to find a restaurant, pet store or the nearest coffee shop. Indeed, more and more consumers search for retail establishments using a mapping application than a general search engine. In many cases the mapping application can provide key data with which the consumer uses to make a selection as to which establishment they will engage. Accuracy of such data, including the location of the establishment, is critical.
  • Search and Social sites including Google®, Facebook®, Yahoo®, Bing®, Foursquare®, and Yelp® all have specific format and data requirements. Other less known but equally as important business applications also has unique format and field requirements. And each may represent the location and content data of a single establishment differently.
  • 123 N. Main St. may be completely different than 123 S. Main St.
  • 123 S. Main St. Consider a consumer traveling in an unfamiliar city and seeking to locate a retail establishment for lunch. Through a search the individual has located a suitable location and is using a navigation app to arrive at the destination. But upon arrival according to the application the desired location is nowhere in sight. Yet a suitable alternative is close at hand and a sale is lost. Accurate and consistent geocoding is a growing concern in commercial enterprises.
  • the loading dock may be a more accurate representation of the retail establishment's address.
  • This sort of error is compounded by the fact that third parties may each associate a technically correct address with different latitude and longitude coordinates.
  • the representation of the same address among various third party mapping applications can vary resulting in a wide disparity in the rendering of a point of interest.
  • Such inconsistencies can have a dramatic impact on sales, consumer recognition and business efficiencies.
  • inaccuracy with respect to secondary fields of data can also adversely impact the success of a retail establishment. Having an inaccurate telephone number or hours of operation can deter customers from interacting with a retail location.
  • What is needed is a system and associated methodology to collect correct locational information, validate and cleanse the data, and compare it against third party sources so as to produce a highly reliable and accurate body of information that can be conveyed consistently.
  • the system and methodology of the present invention addresses these and other needs of the prior art for collecting, validating, modifying and exporting improved locational data.
  • a system and associated methodology manages localization data.
  • a primary set of data associated with one or more specific locations is imported and matched to a predefined format.
  • external, secondary, data associated with each of the localities listed in the primary data set is collected from a plurality of third party location service providers. This includes the identification and collection of potential duplicate sets of secondary data. That is, third party representation of separate locations when in fact they are the same location.
  • a comparison is made between the plurality of secondary data sets and the primary data set. Differences between the data sets are identified and the primary data set modified as necessary.
  • normalized data from the modified primary data set is exported to the third party location service providers to enhance consistency and reliable of locational data.
  • a comparison metric is generated that identifies differences between the primary and secondary data sets. Responsive to the comparison metric reaching a predefined threshold one or more aspects of the primary data set is modified automatically. Moreover the metrics regarding comparison of the primary data to that of secondary data sets and their matching between the sets is historically tracked building a foundation of data on which to base modification decisions.
  • Additional features of the invention can include, a method of localization data, wherein the modified primary set of data includes a modified set of geospatial coordinates based on differences between the primary and plurality of secondary sets of geospatial coordinates.
  • the modified sets of geospatial coordinates are, in another embodiment of the present invention, based on weighted combinations of differences between the primary and the plurality of secondary sets of geospatial coordinates.
  • the data is then normalized according to a predefined format prior to be exported to a designated third party.
  • a system for management of localization data includes a comparison engine operable to compare the primary and secondary set of geospatial coordinate data to form a comparison metric.
  • the comparison engine is further operable to compare each of the plurality of secondary sets of geospatial coordinates with the primary set of geospatial coordinates to form a comparison metric.
  • a modification engine then operates to modify the primary set of data and create a modified primary set of data based on the secondary set of data; the modifications being based on a weighted combination of differences between the primary set of geospatial coordinates and each of the plurality of secondary sets of geospatial coordinates.
  • a normalization engine operable to convert the modified primary set of data to a predefined format consistent with one or more third parties.
  • An export engine is then used to export the modified set of primary data.
  • FIG. 1 presents a high-level block diagram of a system for localization data management according to one embodiment of the present invention
  • FIG. 2 is a high-level flowchart of a methodology, according to one embodiment of the present invention, to manage localization data
  • FIG. 3 is a flowchart of another method embodiment for management of localization data according to the present invention.
  • FIG. 4 is a flowchart for identifying differences between a primary set of location data and a plurality of secondary sets of location data derived from third party location services according to one embodiment of the present invention
  • FIG. 5 is a rendering of a dashboard, according to one embodiment of the present invention, for importing a primary data set into a localization data management system;
  • FIG. 6 is a rendering of a dashboard for the validation and matching of data fields of a primary data set against a standardized template according to one embodiment of the present invention
  • FIG. 7 is a rending of geocoding of the primary locational data set according to one embodiment of the present invention.
  • FIG. 8 is a rending of one embodiment of a dashboard for the comparison and management of localization data representing data associated with a primary data set of a locale as compared to a plurality of secondary data sets of the same locale from one or more third party location services;
  • FIG. 9 is a detailed view of a set of primary data set localities having fair pin placement assessments and an associated geospatial representation according to one embodiment of the present invention.
  • FIG. 10 is geospatial rendition of a plurality of geospatial pins associated with a common location according to one embodiment of the present invention.
  • FIG. 11 is a street view and corresponding geospatial rendering of the locality of FIG. 10 with a corrected geocodes from a primary data set, according to one embodiment of the present invention
  • FIG. 12 depicts a comparison of an inaccurate and/or incomplete primary set of data with that of a plurality of secondary sets of data collected from one or more third party location service providers according to one embodiment of the present invention
  • FIG. 13 shows a corrected primary set of data consistent with secondary set of data collected from a plurality of third party location service providers according to one embodiment of the present invention.
  • FIG. 14 shows an updated dashboard indicating a revised comparison metric based on updated geocoding and external data according to one embodiment of the present invention.
  • a system and associated methodology for management of localization data compares a primary set of data to collected third party information related to the same locale. Based on user inputs and evaluation of a comparison metric to a predefined threshold, locational data can be corrected, normalized and exported to a plurality of third parties consistently, reliably and efficiently.
  • a system establishes a primary data source from a customer or a client.
  • the primary data is imported and mapped to a standard set of fields that are representative of data normally associated with localization data. If necessary, data is geocoded according to a standard format and gaps in the information generally associated with locational data is identified. Third party data associated with each locality is thereafter collected and used to score the validity and accuracy of the primary data source.
  • a scoring, or comparison metric as it is hereafter referred, is determined and while the comparison metric is not necessarily an indication of erroneous data fields it is an indication of disparities between that which a clients holds to be representative locational data and that of one or more third parties that present locational data to the public.
  • Locational data associated with the primary data source that is significantly different from a collected body of third party information can, according to one embodiment of the present invention, be changed automatically based on a comparative analysis of third party data.
  • the user can also validate the accuracy of the primary data manually in light of third party data using a workbench or dashboard. Thereafter the validated and, if necessary, modified data is normalized and presented to various third party applications in a format consistent with those third parties.
  • any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment.
  • the appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
  • the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion.
  • a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and A and B are both true (or present).
  • the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed in the computer or on the other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
  • blocks of the flowchart illustrations support combinations of means for performing the specified functions and combinations of steps for performing the specified functions. It will also be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.
  • FIG. 1 presents a high-level block diagram of a system for localization data management according to one embodiment of the present invention.
  • the system 100 includes an import engine 110 , a collection engine 120 , a management engine 160 and an export engine 170 .
  • the management engine 160 is further comprised of modules operable to compare and match localization data 130 as well as modify 140 such data when necessary.
  • the management engine 160 includes a normalization engine 150 to place localization data into third party specific format prior to exportation.
  • the import engine 110 includes, in one embodiment, a portal by which a primary data set is supplied by a client.
  • Data can be introduced into the system in a variety of formats; raw data fields and spreadsheets including a CVS file having locational data are also imported.
  • the import engine 110 accepts the information in client format and maps the data to a predefined format of industry-accepted fields. These core sets of fields serve as the basis for each location and include, among other things, name, address, location, phone number, operating hours, etc.
  • the import engine 110 maps the supplied data to each of these fields regardless of how they are named or arranged based on common characteristics. For example an address field typically includes a numerical value, a name of street, avenue or boulevard as well as city, state, country and postal code. While each client's format and label may differ the import engine 110 parses the data so as to place it in the correct field. And in some instances data presented by a client is transformed into manageable and understandable packets so that it can be property mapped into the standard fields.
  • the present invention also accepts and store other information that, while not considered necessary with respect to localization data, is nonetheless descriptive of the clients retail or business establishment.
  • Information of this type can include URLs, service descriptions, menus, directions, etc.
  • One aspect of the present invention is to provide feedback to the client as to the depth and health of the client's locational data.
  • the primary data set is analyzed against a set of metrics to determine if the data provides basic information such as name, brand, address, phone, etc. and well as completeness. For example the data supplied may be missing a basic field such as hours of operation.
  • the data set includes a field for phone number for each location may of the localities may find this information to be absent indicating that the primary data set in incomplete.
  • the import engine 110 determines and conveys to the client a metric representing a degree of basic information that has been provided as well as a degree of completeness of that information.
  • This internal data metric provides the client with feedback as to the robustness and completeness of their primary data set, exclusive of its comparison to any third parties. Entries that are either incomplete or lacking in basic information are also flagged so that the client can supply additional information to aid in the effectiveness of the system.
  • Client imported data hereafter referred to as a primary data set, is retained in a database and modified as necessary.
  • a primary data set In addition to storing the data supplied by the client it may be necessary to geocode one or more locations. While the import engine 110 and system 100 is capable of accepting client presented geocodes, the import engine 110 is also operable to geocode supplied addresses into an exact latitude and longitude coordinates (or similar geospatial codes) that are needed for mapping and positioning.
  • the system for management of localization data 100 further collects third party localization data via the collection engine 120 .
  • Each entry of a client's primary set of data includes a specific locality. That locality may represent a retail establishment or a similar commercial location.
  • third party locational data of the same locality is collected and compared to the primary set of data.
  • This plurality of third party secondary data sets each presents a unique representation of the same locality. And in some instances duplicates are identified. That is, representations that appear to be different localities yet are in fact the same location.
  • One objective of the present invention is to identify and correct disparities between these localization representations.
  • the collection engine 120 Using a locality of the primary data set as a basis for the search, the collection engine 120 will initiate an inquire to third party vendors such as Google®, Bing®, Yahoo®, Foursquare® and the like, to gain secondary localization data consistent with the fields mapped by the primary data set. For example address information, geocodes, hours of operation, branding data and the like for each locality are individually collected and stored.
  • third party vendors such as Google®, Bing®, Yahoo®, Foursquare® and the like.
  • the collection engine 120 uses a plurality of different inquires to identify data necessary to conduct a robust and effective comparison of localization data.
  • FIG. 2 presents a basic flowchart, according to one embodiment of the present invention, of a methodology to manage localization data. As shown the process begins 205 with the importation of a primary data set. That data is then compared to collected, secondary, third party data and, if warranted, modified 230 . The role of modification of the primary data set falls to the management engine 160 shown in FIG. 1 .
  • the management engine 160 includes three modules or engines. They are the comparison and matching engine 130 , the modification engine 140 , and the normalization engine 150 . Each of these components of the management engine 160 works to create an accurate modified version of the primary data set that can be exported.
  • the management engine 160 receives data from the import engine 110 and the collection engine 120 and engages in a comparison to ascertain a degree of accuracy for each locality. This process begins with the comparison and matching engine 130 that conducts a field-by-field comparison of the primary data set to each third party secondary data set. As with the primary data set, each secondary data set from each third party must also be mapped to a standard set of fields. Once mapped, each field for each secondary data set can be compared against the corresponding field of the primary data set.
  • This comparison yields an external data metric.
  • This external data metric combined with the internal data metric and a yet to be described geocode comparison, to arrive at an overall comparison metric or score.
  • This score provides the client with an indication of the overall health of their locational data and how well they are effectively providing locational data regarding their establishments to the public.
  • the comparison engine 130 analyzes for a locality each field of a secondary data set against the same field of the primary data.
  • a difference is identified that field and third party source is flagged as being different from the primary source.
  • the phone number listed by the third party for a certain locality may differ than what is provide by the primary data source.
  • Yet another third party source of information may have the correct telephone number but the hours of operation are incorrect. Each of these third party sources would be flagged and the aberrant fields highlighted.
  • pin placement refers to the geocode (latitude and longitude) associated with each locality. It is possible and often likely that the geocode of the primary data source differs from one or more of the geocodes of the secondary data set. This is true even when each secondary data set includes the same address.
  • the comparison and matching engine 130 identifies discrepancies with pin placements between the primary data set and one or more of the secondary data sets provided by third parties. As with external data, differences in pin placement are flagged so that the client can review and if necessary correct the pin placement of the primary data source.
  • Comparison of external data is, as described, distinct. A mistake found in a phone number or an address is flagged as being in accurate and presented for correction. Pin placement however includes a subjective element. For example, it is highly likely that none of the third party geocodes for a particular locality will exactly match the geocode in the primary data set. Yet a certain degree of difference is likely acceptable. For example, if a geocode for a secondary data set is within 10 feet of that of the primary data set, and both are near the actual location, it is likely within a range of accuracy acceptable by the client. Similarly a secondary geocode that presents a pin 1 ⁇ 2 mile from the true location of the establishment presents a different scenario.
  • a similar challenge is presented when a plurality of geocodes presented by third parties appear to be consistently different than the geocodes of the primary data set.
  • the comparison and matching engine 130 in conjunction with the modification engine 140 , determines, based in one embodiment on a weighted average of differences among the geocodes of the primary data set and the secondary data sets, an accepted geocode. This accepted geocode could differ from any of the presented geocodes including that of the primary geocode.
  • the modification engine can not only present revised data to the applicable third parties but also revise the primary data set.
  • the modification engine 140 and the comparison and matching engine 130 can also identify outliers that are not used in such a determination. Moreover each third party representation of a particular value may not be given equal weight.
  • a primary data set may possess thousands of localities. And while it is possible that for each locality a user may review how the primary data set differs from each of the secondary data sets collected from third parties, such an endeavor is often impractical.
  • the present invention captures third party data and analyzes that data along with the primary data provided by the client to determine the most likely and most accurate representation of localization data. And while a weighted average of the collected data can be used to determine a new or modified set of primary data, other techniques known to one of reasonable skill in the relevant art can be used and are contemplated by the present invention.
  • the primary data set can include verified geocodes. While most geocodes are determined based on an location's address, one embodiment of the present invention enables a client to accept a verified set of coordinates from a trusted source. For example a client may instruct an employee at the site in question to transmit exact geocodes from the establishment. The data can then be entered as being a verified set of geocodes inhibiting any further modification regardless of the comparison metric.
  • the normalization engine 150 accepts data from the comparison and matching engine 130 as well as the modification engine 140 to create a normalized 250 set of data. That data is thereafter exported 270 via the export engine 170 to one or more third parties for consideration and implementation.
  • the management of localization data begins 205 with the importation and collection 210 of primary and secondary data sets respectively. A comparison takes place, metrics are determined and in some cases the primary set is modified 230 to reflect a more accurate statement of the locality. The now modified primary data set is then normalized 250 so that is can be exported 270 to one or more third parties, each in a unique format, ending the process 295 .
  • FIGS. 3 and 4 are flowcharts presenting a high-level outline of the process by which localization data is managed according to the present invention.
  • the process outlined in FIG. 3 beings 305 with the mapping 310 of imported data to a standard format as previously described.
  • the primary data set is thereafter validated 320 against industry norms for locational data to determine whether the primary data set lacks certain fields and if certain entries are simply absent.
  • the addresses provided in the primary data set are geocoded 330 so as to provide a primary set of latitude and longitude coordinates.
  • third party data is thereafter collected 340 .
  • the data is also imported into a standard format so that similar fields of data can be compared.
  • the collected third party data is then compared 350 to the primary data set to identify differences between that which the clients possesses and that which is associated with a particular locality by a plurality of third parties.
  • the comparison is scored 360 as is the validation process and analysis of geocodes to arrive at a metric by which a client can assess the health of their localization data.
  • missing or erroneous data is corrected 370 so that it can thereafter be normalized and exported, ending the process 395 .
  • FIG. 4 shows an iterative process, according to one embodiment of the present invention, by which the primary data set is modified based on its comparison with third party data.
  • the process begins 405 with the identification of differences between the data sets 410 .
  • the management system identifies differences in the data for each locality.
  • a comparison metric 420 is generated. This metric, while indicative of the health of the primary set of data also can be compared against a predefined threshold to determine whether the primary data set should be modified. These modifications can be with respect to external data or to the geocodes associated with each locality.
  • the system modifies 460 specific fields of data so at minimize or eliminate the differences. Another analysis is conducted and the process repeated until the primary data set represents an accurate reflection of the locality data.
  • determining when to modify the primary set of data based on a plurality of different secondary data sets requires careful analysis.
  • the provider of the primary set of data is in the best position to provide accurate localization data.
  • the accuracy of the primary data is raised into question.
  • the present invention measures such an instance and, when warranted, modifies the primary data set without further input from the user.
  • FIGS. 5-14 detail an exemplary process by which localization data is imported into the localization management system, third party data is collected and compared to the data, and modifications to the primary data set occur.
  • FIG. 5 depicts, according to one embodiment of the present invention, the selection and importation of a primary data file.
  • a client the owner of a restaurant chain with multiple locations, identifies 510 a primary data file that includes basic information regarding each restaurant location.
  • the user can drag and drop a file such as a CVS file to an upload portal 520 to achieve the same result.
  • Other means by which to provide a primary set of data are contemplated and should not be viewed as a limitation to the present invention.
  • an automated uploading of data from a client site via an API can provide near real time access to newly added fields and changes to locational data.
  • changes to locational data made by the system of the present invention can be downloaded back to the client site to maintain a consistent set of data across the system interface.
  • each restaurant listed in the primary data set includes fields such as store code, name, address, city, state, postal code, country code, phone number, fax number, home page URL, hours of operation, latitude, longitude, a category code, images associated with the location and a general description.
  • FIG. 6 represents a matching between the plurality of fields identified in the primary data set and those of a predefined standard 610 .
  • the names of fields used by a client are the same as those used in the management system of the present invention, however it is important to align the primary data set with a standardized format to ensure that the later comparison can be properly appreciated.
  • a significant aspect of the importation of data is brand or location name recognition. Many companies place significant value on a precise rendering of their brand as associated with locational data. Accordingly part of the importation step is to specifically identify 620 a brand or name that is associated with each locality. In this case the name, “Mexican Grill” is associated with each locality.
  • Geocoding identifies 720 the latitude and longitude associated with each locality.
  • the address provided by the client as part of the primary data set is verified against a national database of accepted addresses. Once verified the address is geocoded to identify a latitude and longitude.
  • the newly determined geocodes are added to the dataset and used for later comparisons.
  • the system can, according to one embodiment of the present invention, independently determine a new set of geocodes based on the provided and verified address. If the geocodes associated with the primary data set are significantly different than those determined by the system, the locality is flagged for further review or, according to one embodiment, modified based on the accepted and verified address.
  • the collection engine 120 gathers secondary data sets regarding the same location from a plurality of third parties. Parties such as Google®, Foursquare®, Factual®, Facebook®, Yellow Pages®, Bing®, Yelp® and the like are queried for data regarding a specific locality. The collection engine also searches and identifies potential duplicate secondary data sets. Often the processes used by third parties to create and maintain a secondary data set of a single location branch creating multiple data sets related to the same locality. From the third party's perspective each is a unique location with unique characteristics, yet all refer to the same primary data set.
  • One objective of the present invention is to identify duplicate secondary data sets and merge them into a single, accurate data set consistent with the primary data. With secondary data in hand, the collected data is mapped to the same standard set of fields and compared against the primary data set. The comparison produces, among others things, a dashboard presenting to the user a summary of the comparison analysis.
  • FIG. 8 presents, according to one embodiment of the present invention, a rendering of a dashboard showing the comparison of a primary set of locational data to a plurality of third party data sets.
  • the dashboard 800 presents a summary panel that includes an overall comparison metric 820 and individual contributing scores. These contributing scores include metrics with respect to data provided 830 , the location of the geocodes (pins) 835 and external data 840 .
  • the dashboard also includes more detailed information regarding the completeness and state of the primary data set 850 as well as an overview of the pin placement 860 in comparison to third party data. Lastly the dashboard 800 provides information of how the external data 870 compares to that of the primary data set for each party.
  • the primary data set includes 20 locations and has an overall score or comparison metric of 76.
  • a score of 100 indicates a perfect correlation between the primary set of data and all third party data while 0 indicates a lack of correlation.
  • Other means by which to measure and convey the health of the primary data are indeed possible and contemplated by the present invention.
  • the dashboard also indicates that the overall score of 76 includes contributing scores of 80 with respect to the completeness and scope of the primary data set, 53 for the correlation of the geocodes associated with the primary data set as compared to those of the third party sources, and 90 for external data.
  • the primary data appears to be relatively complete and external data of third party sources appears to mostly match that presented by the primary data set.
  • geocoding associated with the third party data sets as compared to that of the primary data set shows significant errors.
  • the external data panel 870 depicts inconsistencies between the third party sources. While none of the third party sources exactly matches that of the primary data source, three seem to possess a very high correlation, two are mediocre and two are outliers.
  • the dashboard enables the user to drill down to each locality so as to determine how a particular locality differs from the third party data or from the standard format.
  • 6 locations are flagged as not meeting the standard format requirements for either scope or completeness.
  • one of the flagged localities of the primary data set may have the phone field blank despite the fact that the other data is complete.
  • the pin placement (geocoding) panel 860 identifies pin placement as confirmed, good, fair or poor.
  • the spread of the pins may also be characterized as being close, acceptable, or scattered. In this case 15% of the localities are associated with poor pin placement, 10% fair, 50% good and 25% confirmed.
  • the system enables a user to ascertain more detail as to why a particular locality's pin placement has been assessed as fair, poor or good.
  • FIG. 9 presents, according to one embodiment of the present invention, a rendering of a pin placement analysis for locational data.
  • three locations out of 20 have been determined to possess fair pin placement.
  • Such an assessment is determined, in one embodiment, by assuming that the pin placement of the primary data source is true and determining a collective degree of difference between each of the third party pins to the primary pin.
  • the center of a cluster of pins can be determined to be the true value and differences measured from that location.
  • the first of the three Mexican Grills is located at 154 Hutchinson Ave, in Columbus Ohio.
  • a satellite image 930 of the vicinity of the address shows the placement of each pin along with a representative avatar.
  • the primary data pin 940 is located on Hutchinson Ave as is the pin associated with YP® 945 .
  • the Factual pin 950 is located near the intersection of Hutchinson Ave and High Cross Blvd while the Google® pin 960 , Bing® 970 and Facebook® 980 are appear near a building.
  • the graphic thus represents not only a fair rendering of the geocoding but one that is scattered among the various third party data files.
  • the Google® pin 960 is most representative of the actual location of the restaurant. A user therefore can drag the primary pin 940 to coincide with that of Google 960 and Bing 970 . By doing so the primary data set is modified and the flag removed.
  • FIG. 10 presents another rendering 1010 of a comparison of locational data according to one embodiment of the present invention.
  • the Mexican Restaurant located on Youngfield St. in Wheat Ridge, Colo. 920 is depicted, as are 7 different pin locations. Again the pin placement has been assessed as fair.
  • the primary data pin 1020 (as is YP® 1040 and FourSquare® 1030 ) is located on the street (Youngfield St.) as opposed to being by the retail establishment 1090 .
  • the image in FIG. 10 shows a clear cluster of pins near the same location.
  • Google® 1060 , Bing® 1080 , Factual® 1070 , and Facebook 1050 are near the actual restaurant location 1090 .
  • a comparison of the geocoding data can identify a close correlation of several geocodes at the same locality.
  • Each of the third party sources can additionally posses a rating or score to indicate the confidence on which the system values a particular geocoding.
  • a close correlation by a highly valued third party sources can also be scored and trigger an automatic modification of the primary data geocoding so as to match a central location amongst the cluster.
  • FIG. 11 presents two additional views of the interface for repositioning of locational data according to one embodiment of the present invention.
  • FIG. 11 presents a street image of the cluster 1190 of third party pins 1060 , 1070 , 1050 , as well as the repositioned primary pin 1120 near the front door of the retail location.
  • the lower top satellite view 1010 shows a relocated primary data pin 1120 near positioned within the cluster of third party pins 1050 , 1060 , 1070 , 1080 .
  • FIG. 12 presents a rendering of missing data being supplied by trusted third party sources.
  • the Mexican Grill in Chandler, Ariz. has been flagged 1210 as lacking a phone number.
  • the phone number 1230 of the primary data source has only 9 digits.
  • each of three trusted third party sources 1240 , 1250 , 1260 indicates not only a high correlation with the data that is present with the primary data source (480-783-020 vs. 480-783-0200) but each is the same.
  • the reliability of each third party source can be accessed as can the correlation between various third party sources.
  • An algorithm can determine based on the accessed value and correlation whether a predefined threshold has been reached. If so, the values consistently associated with the secondary data sources can be used to modify the primary data source.
  • the flags associated with each secondary data set 1320 can be replaced with a validation mark showing a consistency between the data shown on each secondary data set 1240 , 1250 , 1260 and the primary data set 1310 .
  • One object of the present invention is to import a primary set of localization data and compare that data to a plurality of secondary data sets derived from unique third party sources.
  • Data from each source are mapped to a standard set of fields wherein discrepancies are determined and conveyed to a user via a dashboard.
  • the comparison of the primary data set to the plurality of secondary data sets produces a comparison metric indicative of the health of the primary data set.
  • the present invention can autonomously determine whether the primary data set should be modified to reflect data held by one or more of the secondary data sets. Once modified, either manually or automatically, the new primary data set can be normalized and exported to each third party in a format uniquely acceptable to that entity.
  • Another feature of the present invention is the ability to update a particular field among a widespread number of third party location providers. For example a business entity that has elected to increase the hours of operation in a geographic region can modify the primary data set with respect to those localities and then export that data to each third party enterprise that provide locational data. In the same way widespread changes to company wide information can be efficiently submitted to each provider before the third party can ascertain the change through their independent methods.
  • modules, managers, functions, systems, engines, layers, features, attributes, methodologies, and other aspects are not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, divisions, and/or formats.
  • the modules, managers, functions, systems, engines, layers, features, attributes, methodologies, and other aspects of the invention can be implemented as software, hardware, firmware, or any combination of the three.
  • a component of the present invention is implemented as software
  • the component can be implemented as a script, as a standalone program, as part of a larger program, as a plurality of separate scripts and/or programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming.
  • the present invention is in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
  • the present invention can be implemented in software and is web based.
  • Software programming code that embodies the present invention is typically accessed by a microprocessor from long-term, persistent storage media of some type, such as a flash drive or hard drive.
  • the software programming code may be embodied on any of a variety of known media for use with a data processing system, such as a diskette, hard drive, CD-ROM, or the like.
  • the code may be distributed on such media, or may be distributed from the memory or storage of one computer system over a network of some type to other computer systems for use by such other systems.
  • the programming code may be embodied in the memory of the device and accessed by a microprocessor using an internal bus.
  • the techniques and methods for embodying software programming code in memory, on physical media, and/or distributing software code via networks are well known and will not be further discussed herein.
  • program modules include routines, programs, objects, components, data structures and the like that perform particular tasks or implement particular abstract data types.
  • program modules include routines, programs, objects, components, data structures and the like that perform particular tasks or implement particular abstract data types.
  • program modules may be located in both local and remote memory storage devices.
  • An exemplary implementation of the present invention may also be executed in a Web environment, where software installation packages are downloaded using a protocol such as the Hypertext Transfer Protocol (HTTP) from a Web server to one or more target computers (devices, objects) that are connected through the Internet.
  • HTTP Hypertext Transfer Protocol
  • an implementation of the present invention may be executing in other non-Web networking environments (using the Internet, a corporate intranet or extranet, or any other network) where software packages are distributed for installation using techniques such as Remote Method Invocation (“RMI”) or Common Object Request Broker Architecture (“CORBA”).
  • Configurations for the environment include a client/server network, as well as a multi-tier environment. Furthermore, it may happen that the client and server of a particular installation both reside in the same physical device, in which case a network connection is not required. (Thus, a potential target system being interrogated may be the local device on which an implementation of the present invention is implemented.)
  • the present invention is a web-based tool that helps marketers and agencies make their location data accurate, accessible and usable.
  • the present invention embodies a set of tools to improve and prepare data using structured and repeatable workflows.
  • the management system of the present invention maintains a central, authoritative repository of location data that can be accessed and manipulated by a user while making that data available across digital marketing channels such as search, social, maps, and mobile access points.

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)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
US14/461,377 2013-08-16 2014-08-16 Location data integration and management Abandoned US20150052152A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/US2014/051383 WO2015024007A2 (fr) 2013-08-16 2014-08-16 Intégration et gestion de données d'emplacement
US14/461,377 US20150052152A1 (en) 2013-08-16 2014-08-16 Location data integration and management
US16/689,955 US11080312B2 (en) 2013-08-16 2019-11-20 Location data integration and management
US17/363,391 US11580142B2 (en) 2013-08-16 2021-06-30 Location data integration and management
US18/154,628 US12271405B2 (en) 2013-08-16 2023-01-13 Location data integration and management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201361866970P 2013-08-16 2013-08-16
US14/461,377 US20150052152A1 (en) 2013-08-16 2014-08-16 Location data integration and management

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/689,955 Continuation US11080312B2 (en) 2013-08-16 2019-11-20 Location data integration and management

Publications (1)

Publication Number Publication Date
US20150052152A1 true US20150052152A1 (en) 2015-02-19

Family

ID=52467589

Family Applications (5)

Application Number Title Priority Date Filing Date
US14/461,377 Abandoned US20150052152A1 (en) 2013-08-16 2014-08-16 Location data integration and management
US16/689,955 Expired - Fee Related US11080312B2 (en) 2013-08-16 2019-11-20 Location data integration and management
US17/363,391 Active US11580142B2 (en) 2013-08-16 2021-06-30 Location data integration and management
US18/154,628 Active US12271405B2 (en) 2013-08-16 2023-01-13 Location data integration and management
US19/090,192 Pending US20250225156A1 (en) 2013-08-16 2025-03-25 Location Data Integration and Management

Family Applications After (4)

Application Number Title Priority Date Filing Date
US16/689,955 Expired - Fee Related US11080312B2 (en) 2013-08-16 2019-11-20 Location data integration and management
US17/363,391 Active US11580142B2 (en) 2013-08-16 2021-06-30 Location data integration and management
US18/154,628 Active US12271405B2 (en) 2013-08-16 2023-01-13 Location data integration and management
US19/090,192 Pending US20250225156A1 (en) 2013-08-16 2025-03-25 Location Data Integration and Management

Country Status (2)

Country Link
US (5) US20150052152A1 (fr)
WO (1) WO2015024007A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116756393A (zh) * 2023-06-09 2023-09-15 北京中科声智科技有限公司 地点信息批量维护方法、装置、电子设备及存储介质

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040260720A1 (en) * 1999-12-22 2004-12-23 Cossins Robert N. Geographic management system
US7477903B2 (en) * 2000-05-20 2009-01-13 Hewlett-Packard Development Company, L.P. Obtaining location updates about a mobile entity for use in a location-sensitive application
US20090275348A1 (en) * 2008-05-02 2009-11-05 Weinreich Andrew P Location-Based Services Platform
US20100238070A1 (en) * 2009-03-18 2010-09-23 Andrew Llc System and method for concurrently determining locations of mobile device in wireless communication network
US20120158704A1 (en) * 2010-12-16 2012-06-21 The Dolan Company Geospatial inconsistencies identification data system based on contractual rights and geographical network analysis
US20130132434A1 (en) * 2011-11-22 2013-05-23 Inrix, Inc. User-assisted identification of location conditions
US20130316696A1 (en) * 2012-05-25 2013-11-28 Carnegie Mellon University Energy Efficient and Accuracy Aware Mobile Services
US20140101180A1 (en) * 2012-10-08 2014-04-10 International Business Machines Corporation Mapping Infrastructure Layout Between Non-Corresponding Datasets
US20140280277A1 (en) * 2013-03-15 2014-09-18 Global Precision Solutions, Llp. System and method for integration and correlation of gis data
US20140280645A1 (en) * 2013-03-14 2014-09-18 Qualcomm Incorporated Methods, Servers and Systems for Verifying Reported Locations of Computing Devices
US8868522B1 (en) * 2012-11-30 2014-10-21 Google Inc. Updating geographic data based on a transaction
US20140357198A1 (en) * 2013-05-28 2014-12-04 Tencent Technology (Shenzhen) Company Limited System and method for locating a mobile device
US20140372420A1 (en) * 2012-12-20 2014-12-18 Google Inc. Systems and Methods for Providing Search Results for Mobile Businesses
US20150026181A1 (en) * 2013-07-17 2015-01-22 PlaceIQ, Inc. Matching Anonymized User Identifiers Across Differently Anonymized Data Sets

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004028061A2 (fr) * 2002-09-20 2004-04-01 Racom Products, Inc. Systeme de telemetrie a transmission sans fil de donnees numeriques/analogiques, conçu pour un procede de distribution d'informations de localisation sur le web, et procede pour developper et distribuer des informations associees a son utilisation
US8229458B2 (en) * 2007-04-08 2012-07-24 Enhanced Geographic Llc Systems and methods to determine the name of a location visited by a user of a wireless device
US8805707B2 (en) * 2009-12-31 2014-08-12 Hartford Fire Insurance Company Systems and methods for providing a safety score associated with a user location
EP2805568A4 (fr) * 2012-01-18 2015-12-16 Kinectus LLC Systèmes et procédés permettant d'établir des communications entre des utilisateurs de dispositifs mobiles

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040260720A1 (en) * 1999-12-22 2004-12-23 Cossins Robert N. Geographic management system
US7477903B2 (en) * 2000-05-20 2009-01-13 Hewlett-Packard Development Company, L.P. Obtaining location updates about a mobile entity for use in a location-sensitive application
US20090275348A1 (en) * 2008-05-02 2009-11-05 Weinreich Andrew P Location-Based Services Platform
US20100238070A1 (en) * 2009-03-18 2010-09-23 Andrew Llc System and method for concurrently determining locations of mobile device in wireless communication network
US20120158704A1 (en) * 2010-12-16 2012-06-21 The Dolan Company Geospatial inconsistencies identification data system based on contractual rights and geographical network analysis
US20130132434A1 (en) * 2011-11-22 2013-05-23 Inrix, Inc. User-assisted identification of location conditions
US20130316696A1 (en) * 2012-05-25 2013-11-28 Carnegie Mellon University Energy Efficient and Accuracy Aware Mobile Services
US20140101180A1 (en) * 2012-10-08 2014-04-10 International Business Machines Corporation Mapping Infrastructure Layout Between Non-Corresponding Datasets
US8868522B1 (en) * 2012-11-30 2014-10-21 Google Inc. Updating geographic data based on a transaction
US20140372420A1 (en) * 2012-12-20 2014-12-18 Google Inc. Systems and Methods for Providing Search Results for Mobile Businesses
US20140280645A1 (en) * 2013-03-14 2014-09-18 Qualcomm Incorporated Methods, Servers and Systems for Verifying Reported Locations of Computing Devices
US20140280277A1 (en) * 2013-03-15 2014-09-18 Global Precision Solutions, Llp. System and method for integration and correlation of gis data
US20140357198A1 (en) * 2013-05-28 2014-12-04 Tencent Technology (Shenzhen) Company Limited System and method for locating a mobile device
US20150026181A1 (en) * 2013-07-17 2015-01-22 PlaceIQ, Inc. Matching Anonymized User Identifiers Across Differently Anonymized Data Sets

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116756393A (zh) * 2023-06-09 2023-09-15 北京中科声智科技有限公司 地点信息批量维护方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
US20210342373A1 (en) 2021-11-04
US11080312B2 (en) 2021-08-03
US20230153334A1 (en) 2023-05-18
US12271405B2 (en) 2025-04-08
US11580142B2 (en) 2023-02-14
WO2015024007A3 (fr) 2015-11-05
WO2015024007A2 (fr) 2015-02-19
US20200089695A1 (en) 2020-03-19
US20250225156A1 (en) 2025-07-10

Similar Documents

Publication Publication Date Title
US8812585B2 (en) Trusted maps: updating map locations using trust-based social graphs
US8918898B2 (en) Methods, apparatus and systems for onsite linking to location-specific electronic records of locate operations
US20070192116A1 (en) Position-sensitive events
US20150302346A1 (en) Methods and systems for optimizing efficiency of a workforce management system
KR20130122525A (ko) 사용자 피드백을 통한 위치 기반 데이터의 증강 및 보정
EP2793179A1 (fr) Procédé de génération de publicités ciblées par l'emplacement et déclenchées par un mot-clé et génération de publicités à couche récupérable d'utilisateur
US10523704B2 (en) Methods and apparatus for identification and ranking of synthetic locations for mobile applications
US11995594B2 (en) Managing technical process data
US20250225156A1 (en) Location Data Integration and Management
CN104750879B (zh) 一种电子地图标注、认领、纠错方法及处理设备
KR102184048B1 (ko) Gis 기반 토지 이용 계획 검토 시스템 및 방법
US20180075383A1 (en) Geolocating entities of interest on geo heat maps
CN114119146A (zh) 一种推荐方法、装置、电子设备及可读存储介质
US12125077B1 (en) Automatic synchronization of payment data across distributed systems
Mauro et al. Analysis of spatial correlation in predictive models of forest variables that use LiDAR auxiliary information
US10685364B2 (en) Method and apparatus for causing a recommendation of a point of interest
Mika Modernisation of the Cadastre in Poland as a tool to improve the land management and administration process
US20160132835A1 (en) Method and system for decision support in relation to geolocalization of a candidate's residence and workplace
US9449110B2 (en) Geotiles for finding relevant results from a geographically distributed set
CN107533686A (zh) 用于监控业务运营的方法和系统
US8823492B2 (en) Detection of incursion of proposed excavation zones into buried assets
JP2012118612A (ja) マーケティング提案支援システム
US20090307042A1 (en) On-the-Spot Labour Market Providing Support System
Ryerson et al. The role of remote sensing in assisted development: experience drawn from work in over 40 countries
US20250053703A1 (en) System and methods for generating multi-dimensional models and reports

Legal Events

Date Code Title Description
AS Assignment

Owner name: PLACEABLE, COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAUFMAN, ARI;MEIER, JAKE;WEINER, DANIEL;REEL/FRAME:042040/0530

Effective date: 20140820

AS Assignment

Owner name: IGNITE LOCAL SEARCH SOLUTIONS, INC., TEXAS

Free format text: CERTIFICATE OF CONVERSION;ASSIGNOR:PLACEABLE, LLC;REEL/FRAME:043609/0274

Effective date: 20170503

AS Assignment

Owner name: PLACEABLE, LLC, TEXAS

Free format text: MEMBERSHIP INTEREST PURCHASE AGREEMENT CONFIRMING ASSIGNEE NAME;ASSIGNOR:PLACEABLE;REEL/FRAME:044114/0689

Effective date: 20170421

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCB Information on status: application discontinuation

Free format text: ABANDONMENT FOR FAILURE TO CORRECT DRAWINGS/OATH/NONPUB REQUEST