Bank customer grid management method based on geographic space relationship

Abstract

The invention discloses a bank customer grid management method based on a geographic space relationship, and belongs to the technical field of geographic information processing. A bank customer grid management method based on a geographic space relationship comprises the following steps: S1, creating a geographic grid by selecting a single or multiple polygons or administrative divisions on a map, and storing the created geographic grid in a database in a WKT text form; s2, obtaining accurate longitude and latitude coordinate points of the customer through an on-site visiting or address decoding function, storing the accurate longitude and latitude coordinate points into a database, and binding the accurate longitude and latitude coordinate points with customer information; s3, reading the WKT text and the longitude and latitude coordinate points of the customer in the database, and establishing a binding relationship between the customer and the geographic grid through a point-surface relationship between the longitude and latitude coordinate points of the customer and the corresponding region of the geographic grid; and S4, one or more customer managers are set up for each geographic grid to establish a customer-grid-customer manager association relationship, and the association relationship is applied to various field scenes.

Description

Technical Field

[0001] The invention belongs to the field of geographic information processing technology, and more specifically, relates to a method for managing bank customer grids based on geographic spatial relationships. Background Art

[0002] With the development of information technology, it is becoming increasingly important to manage and utilize customers' standardized address information. For enterprises, government agencies and developers, customer address information can improve business efficiency and reduce operating costs. For the financial industry, customer address information can improve the efficiency of a series of marketing activities such as field visits and task assignments. For the logistics industry, customer address information can significantly improve delivery efficiency. For the e-commerce field, customer address information can reduce buyers' input errors when placing orders and shorten order time.

[0003] However, the existing address standardization technology still has problems such as inconsistent administrative division standards, low freedom of user-defined areas, and unclear allocation of users and customers, which cannot meet the needs of specific business scenarios; the low freedom of user-defined areas is because the existing regional division does not support customized division according to user needs; the unclear allocation of users and customers is due to the fact that the grid management relationship between customers and account managers in the existing technology is time-consuming and labor-intensive, the geographical location judgment has large deviations, and the customer affiliation relationship is unclear. Taking a geographic location-based insurance grid data processing method and device (202410917011.X) disclosed in a Chinese invention patent document as an example, the invention uses a geographic location distribution model to obtain insurance grid geographic location data, and through grid division, divides smaller grids in high-density areas, thereby solving the problem of uneven customer distribution due to geographic location; however, the administrative division of this scheme is only the initialization of a five-segment address, and does not take into account the autonomous regions and county-level cities established by the administrative divisions of the Civil Affairs Bureau standards. At the same time, the user-defined area has low freedom and cannot be directly applied to real business scenarios and business systems.

[0004] Therefore, we need a method for managing bank customer grids based on geographic spatial relationships to improve the accuracy of geographic grid divisions, realize the customized needs of account managers in field customer development, improve work efficiency, and reduce the burden on account managers. Summary of the invention

[0005] The purpose of the present invention is to provide a method for managing bank customer grids based on geographic spatial relationships. By creating a geographic grid to match the customer's latitude and longitude coordinates, a binding relationship between the customer and the geographic grid is established. While improving the accuracy of administrative divisions, the geographic area can be customized according to the needs of customer managers and directly applied to real business scenarios, thereby improving work efficiency and reducing the burden on customer managers.

[0006] To achieve the above object, the present invention provides the following technical solutions: A method for managing bank customer grids based on geographic spatial relationships of the present invention comprises the following steps: S1. Create a geographic grid by selecting multiple longitude and latitude coordinate points on the map to form a polygon or administrative division with closed lines between the points, and save the created geographic grid in the form of WKT text in the database; S2. Obtain the precise longitude and latitude coordinates of the customer through on-site visits or address decoding functions, store the longitude and latitude coordinates in the database, and bind them to the customer information in the database; S3. Read the WKT text and the customer's longitude and latitude coordinates in the database, and determine the point-to-surface relationship between the customer's longitude and latitude coordinates and the corresponding area of ​​the geographic grid to establish a binding relationship between the customer and the geographic grid; S4. Each geographical grid shall have one or more account managers who are responsible for managing and maintaining all customers in the grid.

[0007] The geographic grid creation is to correct the geographic fence and the map base map and merge them into a geographic area grid; this creation process first involves the drawing of the first-level grid area, the allocation of responsibilities for the first-level grid and the preservation of the first-level grid information; then the first-level grid push is received and the second-level grid area is drawn, the second-level grid responsibilities are allocated and the second-level grid information is preserved; the customer's precise geographic coordinates are obtained through the customer manager's visit to the registration address and the customer address resolution aggregation method, and the position relationship between points and surfaces is judged with the established geographic grid, so as to obtain the relationship between customer-geographic grid-account manager.

[0008] As a further improvement of the present invention, the polygon or administrative division described in step S1 may be composed of a single polygon or multiple polygons.

[0009] As a further improvement of the present invention, the method for creating a geographic grid comprises the following steps: S1-1. Draw a first-level area and select the first-level grid type as administrative area or characteristic area; S1-2. Backfill the estimated number of customers based on the regional size; S1-3. Select whether the responsibility type is a competitive grid. If it is a competitive grid, you need to set the upper limit and duration of claiming, and finally choose to push it to the affiliated institution; S1-4. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the primary grid type; S1-5. Receive the primary grid push and draw the secondary area, select the secondary grid type to match the primary grid type; S1-6. Backfill the estimated number of customers based on the regional size; S1-7. Select whether the responsibility type is a competitive grid. If it is a competitive grid, you need to set the upper limit and duration of claiming, and finally choose to push it to the affiliated institution and the affiliated account manager; S1-8. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the secondary grid type.

[0010] As a further improvement of the present invention, the backfilling of the estimated number of customers based on the regional size described in step S1-2 and step S1-6 is to estimate the number of potential customers in a specific area by analyzing the population size, consumption capacity or related indicators in the area, thereby improving the accuracy of the subsequent claim upper limit and claim duration, making the process of allocation to the affiliated institution more reasonable.

[0011] As a further improvement of the present invention, the competitive grid described in step S1-3 and step S1-7 is a competitive relationship for resource allocation or management responsibility between different grids or regions in geographic grid management, which needs to be managed and regulated by setting up an affiliation agency to determine the upper limit and duration of claiming, so as to ensure the reasonable allocation of resources and effective management of the grid.

[0012] As a further improvement of the present invention, the method for obtaining the precise longitude and latitude coordinate points in step S2 is to perform geolocation through mobile phones and tablet mobile devices during the user's field visit or to convert the customer's detailed address into longitude and latitude coordinate points by using the address decoding function.

[0013] As a further improvement of the present invention, the step of address decoding processing includes: S2-1. Import the customer address and determine whether the customer already has address data. If the customer already has address data, the original address data will be obtained and added to the manual review page, and the editable original address, current address and address resolution results will appear. If the customer does not have address data, the current address will be added to the manual review page, and the editable current address and address resolution results will appear; S2-2. Add the new address data to the anchor list and the old address to the ignored address library; S2-3. The anchor point list will start the engine to run batches, perform real-time calculations on these address data batches, update the relevant lists after processing, and generate GIS maps based on the processed data; S2-4. The account manager verifies and corrects the customer's new address based on the GIS map. If the new address is wrong, the account manager will be prompted with the error and the address will be added to the ignored database.

[0014] As a further improvement of the present invention, the engine runs a batch of subtasks of batch calculation of new address data in the response anchor list, scanning the standardized addresses corresponding to the new address data, including province, city, district / county, town / street, village / community and house number information.

[0015] As a further improvement of the present invention, the account manager in step S4 can obtain customers through grid allocation, specified or customized methods; the customized method can set the management account affiliation, address affiliation and manually specified allocation priority to adapt to real business scenarios.

[0016] As a further improvement of the present invention, the geographic grid can improve the grid configuration by responding to the maintenance of provinces / cities / districts / streets (townships) / communities (villages). After improving the grid configuration by adding / modifying / deleting grids, the improved grids are synchronized to the grid allocation process, and the customer allocation operation is further improved synchronously; customer relationship configuration and maintenance operations are performed during customer allocation, and after completion, it is determined whether the improvement process is related to customer transactions. If not, the maintenance can be completed. If so, the statistical stage is entered, and public / custom indicators are displayed for customers to reflect customer satisfaction with grid improvement.

[0017] Compared with the prior art, the beneficial effects of the present invention are as follows: a method of managing bank customer grids based on geographic spatial relationships of the present invention constructs a geographic area grid, and obtains the customer's precise geographic coordinates by means of customer manager visiting the registration address and customer address parsing, and judges the position relationship between points and surfaces with the established geographic grid, thereby obtaining the association relationship between customer-grid-account manager, and applying the relationship to offline visits, tasks and marketing scenarios; by clarifying the administrative division standards, the accuracy rate from obtaining customer addresses to administrative divisions is improved, and customers can be classified and managed in geographic space more quickly and accurately, thereby improving the efficiency of customer management; by setting up primary grids and secondary grids, as well as the concept of competitive grids, resources and management responsibilities can be allocated more reasonably to ensure the rational use of resources and effective management of grids; by supporting customer managers to freely edit geographic spatial polygons, different types of geographic areas that meet the needs of offline tasks of customer managers are established, and customized needs for field customer development in the same industry are realized; at the same time, the method of the present invention can be adjusted according to different business needs and market changes, and has good flexibility and scalability. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A schematic diagram of a flow chart of a method for customer management based on geographic spatial relationships of the present invention; Figure 2 A schematic diagram of the process of creating a geographic grid according to the present invention; Figure 3This is a schematic diagram of the customer address resolution process of the present invention; Figure 4 A flow chart is generated for the address resolution-grid allocation-grid relationship of the present invention. DETAILED DESCRIPTION

[0019] Specific embodiment 1: Please refer to Figure 1-Figure 4 A method for bank customer grid management based on geographic spatial relationship includes the following steps: S1. Create a geographic grid by selecting multiple longitude and latitude coordinate points on the map to form a polygon or administrative division with closed lines between the points, and save the created geographic grid in the database in the form of WKT text.

[0020] Specifically, the creation of the geographic grid in step S1 is to correct the geographic fence and the map base map and merge them into a geographic area grid; this creation process first involves the drawing of the first-level grid area, the allocation of responsibilities for the first-level grid, and the preservation of the first-level grid information; then the first-level grid push is received and the second-level grid area is drawn, the second-level grid responsibilities are allocated, and the second-level grid information is preserved; the customer's precise geographic coordinates are obtained by the customer manager visiting the registration address and the customer address resolution aggregation method, and the position relationship between points and surfaces is judged with the established geographic grid, so as to obtain the relationship between customer-geographic grid-account manager.

[0021] Specifically, the polygon or administrative division described in step S1 may be composed of a single polygon or multiple polygons.

[0022] Specifically, the following is an example code of the spatial relationship between the longitude and latitude coordinate points and the geographic grid in step S1: public AddressResultVO childrenMatching(Point point) The current administrative division is level 5 or level 4 and there is no next-level administrative division, and the matching results are returned: if (this.level == 5 || (this.level == 4&&Objects.isNull(this.children))) { AddressResultVO addressResultVO = new AddressResultVO(); BeanUtils.copyProperties(this, addressResultVO); addressResultVO.setStatus(0); addressResultVO.setLng(point.getX()); addressResultVO.setLat(point.getY()); return addressResultVO; } Traverse and search administrative divisions: for (GeoInfoDTO geoInfoDTO : this.children){ Dealing with missing administrative fences: if (Objects.isNull(geoInfoDTO.getGrid())) { continue; } Determine the containment relationship between the point object and the fence of the administrative division: if (geoInfoDTO.getGrid().contains(point)){ If the containment relationship is established, continue to match the next level of administrative divisions: return geoInfoDTO.childrenMatching(point); } } If the next level administrative division is not matched, the current administrative division information is returned: AddressResultVO addressResultVO = new AddressResultVO(); BeanUtils.copyProperties(this, addressResultVO); addressResultVO.setStatus(0); addressResultVO.setLng(point.getX()); addressResultVO.setLat(point.getY()); return addressResultVO.

[0023] } }.

[0024] Specifically, the geographic grid of step S1 can improve the grid configuration by responding to the maintenance of the province / city / district / street (township) / community (village).

[0025] Specifically, the method for creating a geographic grid includes the following steps: S1-1. Draw a first-level area and select the first-level grid type as administrative area or characteristic area; S1-2. Backfill the estimated number of customers based on the regional size; S1-3. Select whether the responsibility type is a competitive grid. If it is a competitive grid, you need to set the upper limit and duration of claiming, and finally choose to push it to the affiliated institution; S1-4. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the primary grid type; S1-5. Receive the primary grid push and draw the secondary area, select the secondary grid type to match the primary grid type; S1-6. Backfill the estimated number of customers based on the regional size; S1-7. Select whether the responsibility type is a competitive grid. If it is a competitive grid, you need to set the upper limit and duration of claiming, and finally choose to push it to the affiliated institution and the affiliated account manager; S1-8. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the secondary grid type.

[0026] Specifically, backfilling the estimated number of customers based on the regional size as described in step S1-2 and step S1-6 estimates the number of potential customers in a specific area by analyzing the population size, consumption capacity or related indicators in the area, thereby improving the accuracy of the subsequent claim upper limit and claim duration, making the process of allocation to the affiliated institution more reasonable.

[0027] Specifically, the competitive grid described in step S1-3 and step S1-7 is the competitive relationship between different grids or regions in resource allocation or management responsibility in geographic grid management, which needs to be managed and regulated by setting up an affiliation agency to determine the upper limit and duration of claiming, so as to ensure the reasonable allocation of resources and effective management of the grid.

[0028] Specifically, the following is a code example for creating a geographic grid: public String createTopRegionGrid(TopRegionGridDTO topRegionGridDTO){ if (regionGridUtilsService.checkGridNameExist(topRegionGridDTO.getGridName(), topRegionGridDTO.getGridLevel())) { throw new ServiceException("Grid creation failed, the grid name already exists"); } Create a grid object and insert it into the database: RegionGrid regionGrid = new RegionGrid(); BeanUtils.copyProperties(topRegionGridDTO, regionGrid); regionGridMapper.insert(regionGrid); Long gridId = regionGrid.getGridId(); Mesh creation rule verification: if (topRegionGridDTO.getGridDutyType().equals("1")&&topRegionGridDTO.getGridUserRelateDTOList().size() != 1) { throw new ServiceException("Only a single organization can be selected when the assignment type is responsibility grid"); } if (topRegionGridDTO.getGridDutyType().equals("2")&&topRegionGridDTO.getGridUserRelateDTOList().size()<2) { throw new ServiceException("Multiple organizations need to be selected when the allocation type is competitive grid"); } Bind the organization and its account managers to the grid and insert them into the database: topRegionGridDTO.getGridUserRelateDTOList().forEach(gridRelateDTO ->{ RegionUserRelate regionUserRelate = new RegionUserRelate(); BeanUtils.copyProperties(gridRelateDTO, regionUserRelate); regionUserRelate.setGridId(gridId); regionUserRelateMapper.insert(regionUserRelate); }); Save the administrative division structure tree corresponding to the grid and insert it into the database: topRegionGridDTO.getAdminDivisionDTOList().forEach(gridAdminDivisionDTO ->{ Integer level = codeSizeToLevel.get(gridAdminDivisionDTO.getCode().length()); if(level == 5){ Bind the five-level administrative divisions to the grid and insert them into the database: RegionAdminDivisionRelate regionAdminDivisionRelate = newRegionAdminDivisionRelate(); regionAdminDivisionRelate.setCode(gridAdminDivisionDTO.getCode()); regionAdminDivisionRelate.setGridId(gridId); regionAdminDivisionRelateMapper.insert(regionAdminDivisionRelate); } String parentCode =gridAdminDivisionDTO.getCode().subSequence(0,levelToParentCode.get(level)).toString(); RegionAddressTree regionAddressTree = new RegionAddressTree(); regionAddressTree.setGridId(gridId); regionAddressTree.setCode(gridAdminDivisionDTO.getCode()); regionAddressTree.setLabel(gridAdminDivisionDTO.getLabel()); regionAddressTree.setLevel(level); regionAddressTree.setParentCode(parentCode); regionAddressTreeMapper.insert(regionAddressTree); }); Update the grid to correspond to the geographic area polygons and save the WKT text to the database: List <string>codeLevel5 = topRegionGridDTO.getAdminDivisionDTOList().stream() .map(RegionAdminDivisionDTO::getCode) .filter(code ->codeSizeToLevel.get(code.length()) == 5) .collect(Collectors.toList()); if (!gridAreaFenceService.updateGridFence("1", gridId, codeLevel5)) { throw new ServiceException("Grid fence save failed!"); } gridInfoRedisService.cleanGridInfo("1"); return "The first level grid was created successfully!"; }.

[0029] S2. Obtain the precise longitude and latitude coordinates of the customer through field visits or address decoding functions, store the longitude and latitude coordinates in the database, and bind them with the customer information in the database.

[0030] Specifically, the precise longitude and latitude coordinates in step S2 are obtained by performing geolocation through mobile phones and tablet devices during the user's field visit or by using the address decoding function to convert the customer's detailed address into longitude and latitude coordinates.

[0031] Specifically, the address decoding process includes: S2-1. Import the customer address and determine whether the customer already has address data. If the customer already has address data, the original address data will be obtained and added to the manual review page, and the editable original address, current address and address resolution results will appear. If the customer does not have address data, the current address will be added to the manual review page, and the editable current address and address resolution results will appear; S2-2. Add the new address data to the anchor list and the old address to the ignored address library; S2-3. The anchor point list will start the engine to run batches, perform real-time calculations on these address data batches, update the relevant lists after processing, and generate GIS maps based on the processed data; S2-4. The account manager verifies and corrects the customer's new address based on the GIS map. If the new address is wrong, the account manager will be prompted with the error and the address will be added to the ignored database.

[0032] Specifically, in step S2-3, the engine runs a batch of subtasks for batch calculation of new address data in the response anchor list, scanning the standardized addresses corresponding to the new address data, including province, city, district / county, town / street, village / community and house number information.

[0033] Specifically, the following is a sample code for obtaining the five-level administrative divisions corresponding to the latitude and longitude coordinate points: public AddressResultVO addressStandardize(String address){ Convert the address to longitude and latitude coordinate system through external interface: BaiduResponseDTO geocoding = baiduApiService.geocoding(address); if(geocoding.getStatus() != 0 || Objects.isNull (geocoding.getResult())){ Exception information returned after an external interface error: AddressResultVO addressResultVO = new AddressResultVO(); addressResultVO.setStatus(1); addressResultVO.setMsg("Failed to convert Baidu address to latitude and longitude"); return addressResultVO; } Convert the latitude and longitude coordinate system to a point object: Point point = geometryFactory.createPoint(new Coordinate(geocoding.getResult().getLocation().getLng(), geocoding.getResult().getLocation().getLat())); Traverse and search administrative divisions: for(GeoInfoDTO geoInfoDTO : geoInfoDTOList){ Determine the containment relationship between the point object and the fence of the administrative division: if(geoInfoDTO.getGrid().contains(point)){ If the containment relationship is established, continue to match the next level of administrative divisions: return geoInfoDTO.childrenMatching(point); } } If not in Zhejiang Province, the following information will be returned: AddressResultVO addressResultVO = new AddressResultVO(); addressResultVO.setStatus(999); addressResultVO.setLng(point.getX()); addressResultVO.setLat(point.getY()); addressResultVO.setMsg("This address is not in Zhejiang Province"); return addressResultVO; }.

[0034] S3. Read the WKT text and the customer's longitude and latitude coordinates in the database, and determine the point-to-surface relationship between the customer's longitude and latitude coordinates and the corresponding area of ​​the geographic grid to establish a binding relationship between the customer and the geographic grid.

[0035] S4. Each geographical grid shall have one or more account managers who are responsible for managing and maintaining all customers in the grid.

[0036] Specifically, in step S4, the account manager can obtain customers through grid allocation, designated or customized methods; the customized method can set the management account ownership, address ownership and manually designated allocation priority to adapt to real business scenarios.

[0037] Specifically, after improving the grid configuration by adding / modifying / deleting grids, the improved grid is synchronized to the grid allocation process, and the customer allocation operation is further improved synchronously; customer relationship configuration and maintenance operations are performed during customer allocation, and after completion, it is determined whether the improvement process is related to customer transactions. If not, maintenance can be completed. If so, the statistical stage is entered, and public / custom indicators are displayed for customers to reflect customer satisfaction with grid improvement; this helps management make macro decisions, such as resource allocation and regional market strategy adjustments.

[0038] Specifically, the following is a sample code for the grid allocation: public String createVirtualGrid(VirtualGridDTO virtualGridDTO) { Create a rule check: virtualGridDTO.checkValid(); VirtualGrid virtualGrid = new VirtualGrid(); BeanUtils.copyProperties(virtualGridDTO, virtualGrid); After selecting the custom configuration rule, set the batch run identifier and run the batch according to the rule to obtain the management relationship: if (virtualGridDTO.getGridAssignType().equals("2")) { virtualGrid.setGridDutyType("2"); virtualGrid.setBatchFlag(Boolean.TRUE); } else { virtualGrid.setBatchFlag(Boolean.FALSE); } SysDept sysDept = sysDeptMapper.selectDeptById(SecurityUtils.getDeptId()); virtualGrid.setDeptType(sysDept.getDeptType()); virtualGridMapper.insert(virtualGrid); Long gridId = virtualGrid.getGridId(); Insert customer: virtualGridDTO.getCustDTOList().forEach(virtualGridCustDTO ->{ VirtualCust virtualCust = new VirtualCust(); BeanUtils.copyProperties(virtualGridCustDTO, virtualCust); Set the customer type: CustTypeEnum custType = CustTypeEnum.getByName(virtualGridCustDTO.getCustType()); virtualCust.setCustType(custType); Set the client certificate type: CustIdTypeEnum custIdType = CustIdTypeEnum.getByName(virtualGridCustDTO.getCustIdType()); virtualCust.setCustIdType(custIdType); virtualCust.setGridId(gridId); virtualCustMapper.insert(virtualCust); }); Assign an account manager and insert the account manager and the account-account manager relationship: if (virtualGridDTO.getGridAssignType().equals("1")) { Insert Account Manager: virtualGridDTO.getGridUserRelateDTOList().forEach(gridUserRelateDTO ->{ if (gridUserRelateDTO.getRelateType().equals("2")) { throw new ServiceException("Virtual grid creation failed and organization cannot be bound"); } VirtualUser virtualUser = new VirtualUser(); BeanUtils.copyProperties(gridUserRelateDTO, virtualUser); virtualUser.setGridId(gridId); virtualUserMapper.insert(virtualUser); Insert a client-account manager relationship: virtualGridDTO.getCustDTOList().forEach(virtualGridCustDTO ->{ VirtualCustUser virtualCustUser = new VirtualCustUser(); BeanUtils.copyProperties(gridUserRelateDTO, virtualCustUser); virtualCustUser.setGridId(gridId); virtualCustUser.setCustId(virtualGridCustDTO.getCustId()); virtualCustUserMapper.insert(virtualCustUser); }); }); } else if (virtualGridDTO.getGridAssignType().equals("2")) { Insert grid assignment rules: virtualGridDTO.getVirtualGridRuleDTOList().forEach(virtualGridRuleDTO->{ VirtualGridRule virtualGridRule = new VirtualGridRule(); BeanUtils.copyProperties(virtualGridRuleDTO, virtualGridRule); Set the rule type: virtualGridRule.setRelateType(CustTypeEnum.getByName(virtualGridRuleDTO.getRelateType())); virtualGridRule.setGridId(gridId); virtualGridRuleMapper.insert(virtualGridRule); }); } gridInfoRedisService.cleanGridInfo("3"); return "Virtual grid created successfully!"; }.

[0039] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.< / string>

Claims

1. A method for managing bank customer grids based on geographic spatial relationships, characterized in that: The following steps are involved: S1. Create a geographic grid by selecting multiple longitude and latitude coordinate points on the map to form a polygon or administrative division with closed lines between the points, and save the created geographic grid in the form of WKT text in the database; S2. Obtain the precise longitude and latitude coordinates of the customer through on-site visits or address decoding functions, store the longitude and latitude coordinates in the database, and bind them to the customer information in the database; S3. Read the WKT text and the customer's longitude and latitude coordinates in the database, and determine the point-to-surface relationship between the customer's longitude and latitude coordinates and the corresponding area of ​​the geographic grid to establish a binding relationship between the customer and the geographic grid; S4. Each geographical grid shall have one or more account managers responsible for managing and maintaining all customers in the grid; The geographic grid creation is to correct the geographic fence and the map base map and merge them into a geographic area grid; this creation process first involves the drawing of the first-level grid area, the allocation of responsibilities for the first-level grid and the preservation of the first-level grid information; then the first-level grid push is received and the second-level grid area is drawn, the second-level grid responsibilities are allocated and the second-level grid information is preserved; the customer's precise geographic coordinates are obtained through the customer manager's visit to the registration address and the customer address resolution aggregation method, and the position relationship between points and surfaces is judged with the established geographic grid, so as to obtain the relationship between customer-geographic grid-account manager.

2. A method for managing bank customer grids based on geographic spatial relationships according to claim 1, characterized in that: The polygon or administrative division described in step S1 may be composed of a single or multiple components.

3. The method for managing bank customer grid based on geographic spatial relationship according to claim 1, characterized in that: The method for creating a geographic grid comprises the following steps: S1-1. Draw a first-level area and select the first-level grid type as administrative area or characteristic area; S1-2. Backfill the estimated number of customers based on the regional size; S1-3. Select whether the responsibility type is a competitive grid. If it is a competitive grid, you need to set the upper limit and duration of claiming, and finally choose to push it to the affiliated institution; S1-4. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the primary grid type; S1-5. Receive the primary grid push and draw the secondary area, select the secondary grid type to match the primary grid type; S1-6. Backfill the estimated number of customers based on the regional size; S1-7. Select whether the responsibility type is a competitive grid. If it is a competitive grid, you need to set the upper limit and duration of claiming, and finally choose to push it to the affiliated institution and the affiliated account manager; S1-8. Save the created geographic grid in the form of WKT text to the database and jump to the corresponding grid query homepage according to the secondary grid type.

4. A method for managing bank customer grids based on geographic spatial relationships according to claim 3, characterized in that: The backfilling of the estimated number of customers according to the regional scale described in step S1-2 and step S1-6 is to estimate the number of potential customers in a specific region by analyzing the population, consumption capacity or related indicators in the region.

5. The method for managing bank customer grid based on geographic spatial relationship according to claim 3, characterized in that: The competitive grid described in step S1-3 and step S1-7 is the competitive relationship between different grids or regions in the resource allocation or management responsibility in the geographic grid management. It needs to be managed and adjusted by setting up an affiliation agency to determine the upper limit and duration of claiming rules to ensure the reasonable allocation of resources and the effective management of the grid.

6. The method for managing bank customer grid based on geographic spatial relationship according to claim 1, characterized in that: The method for obtaining the precise longitude and latitude coordinate points in step S2 is to perform geographic positioning through mobile phones and tablet mobile devices during the user's field visit or to convert the customer's detailed address into longitude and latitude coordinate points by using the address decoding function.

7. A method for managing bank customer grids based on geographic spatial relationships according to claim 6, characterized in that: The steps of address decoding processing include: S2-1. Import the customer address and determine whether the customer already has address data. If the customer already has address data, the original address data will be obtained and added to the manual review page, and the editable original address, current address and address resolution results will appear. If the customer does not have address data, the current address will be added to the manual review page, and the editable current address and address resolution results will appear; S2-2. Add the new address data to the anchor list and the old address to the ignored address library; S2-3. The anchor point list will start the engine to run batches, perform real-time calculations on these address data batches, update the relevant lists after processing, and generate GIS maps based on the processed data; S2-4. The account manager verifies and corrects the customer's new address based on the GIS map. If the new address is wrong, the account manager will be prompted with the error and the address will be added to the ignored database.

8. A method for managing bank customer grids based on geographic spatial relationships according to claim 7, characterized in that: In step S2-3, the engine runs a batch of subtasks for batch calculation of new address data in the response anchor list, scanning the standardized addresses corresponding to the new address data, including province, city, district / county, town / street, village / community and house number information.

9. The method for managing bank customer grids based on geographic spatial relationships according to claim 1, characterized in that: In step S4, the account manager can obtain customers through grid allocation, designated or customized methods; the customized method is to set the management account ownership, address ownership and manually designated allocation priority to adapt to real business scenarios.

Images