CN114153931B - Electronic map version management system and method in grid data system - Google Patents
Electronic map version management system and method in grid data system Download PDFInfo
- Publication number
- CN114153931B CN114153931B CN202111487843.5A CN202111487843A CN114153931B CN 114153931 B CN114153931 B CN 114153931B CN 202111487843 A CN202111487843 A CN 202111487843A CN 114153931 B CN114153931 B CN 114153931B
- Authority
- CN
- China
- Prior art keywords
- version
- grid
- module
- release
- date
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 16
- 238000007689 inspection Methods 0.000 claims abstract description 22
- 238000007726 management method Methods 0.000 claims description 10
- 238000012550 audit Methods 0.000 description 4
- 230000003442 weekly effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000003908 quality control method Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S10/00—Systems supporting electrical power generation, transmission or distribution
- Y04S10/50—Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
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)
- Processing Or Creating Images (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses an electronic map version management system and method in a grid data system, wherein the system comprises the following steps: setting a version update period, version release date and time of each update, version submission expiration date and time of each update, coverage rate and an overlapping rate threshold value of the electronic map; creating grid boundaries of each level in the electronic map based on the initial boundary data of each level to form an initial version and publishing; automatically creating and generating a new version as a version to be used when each new update period starts; drawing grid boundaries of each level in the electronic map based on the current boundary data of each level; detecting whether the coverage rate and the overlapping rate of the grid boundaries of each level are larger than or equal to the corresponding coverage rate threshold value and the overlapping rate threshold value, if so, passing the quality inspection, and if not, refusing to carry out grid drawing again; submitting the version to be used when the submitting time reaches the version submitting deadline and time; auditing a version to be used; when the release time reaches the release date and time of the version, the version to be used is automatically released.
Description
Technical Field
The invention relates to the technical field of electronic map version management, in particular to an electronic map version management system and method in a grid data system.
Background
In the conventional administrative system, a certain version of electronic map can be submitted to be effective immediately after being drawn, and the drawn electronic map under the conventional administrative system is not subjected to quality detection and other operations, so that the effective electronic map is inaccurate. Moreover, the existing version update is self-updated when the user needs to update, and no version update plan exists.
Disclosure of Invention
The invention provides a system and a method for managing electronic map versions in a grid data system, aiming at the problems and the defects existing in the prior art.
The invention solves the technical problems by the following technical proposal:
the invention provides an electronic map version management system in a grid data system, which is characterized by comprising a version plan setting module, an initial version creation and release module, a version creation and generation module, a grid drawing module, a grid quality inspection module, a version submitting module, a version auditing module and a version release module;
the version plan setting module is used for setting a version update period, a version release date and a version release time of each update, a version submission expiration date and a version submission expiration time of each update, and setting a coverage rate threshold and an overlap rate threshold of the electronic map by a user, wherein the version submission expiration date is earlier than the version release date, the coverage rate refers to the total area of each region of a next level under a grid data system in the electronic map, the total area of each region of the next level is overlapped, the area of a region of a last level corresponding to the next level is overlapped, and the overlap rate refers to the total area of each region of the next level is overlapped, and the area of a region of the last level corresponding to the next level is overlapped;
the initial version creating and issuing module is used for creating grid boundaries of polygonal shapes of all levels in the electronic map based on initial boundary data of all levels in the grid data system so as to form an initial version serving as a base line version and issuing, wherein the grid boundary of the next level is positioned in the grid boundary of the last level;
the version creation generation module is used for automatically creating and generating a new version to be used as a version to be used based on the version before the new update period starts when the new update period starts each time, automatically creating and generating the version release date, the version release time, the version submission expiration date and the version submission expiration time of the version to be used based on the version plan, taking the version before the new update period starts as a base line version, and automatically naming the version to be used based on the name of the base line version, wherein the name of the version to be used is editable;
the grid drawing module is used for drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels in a grid data system;
the grid quality inspection module is used for detecting whether the coverage rate of the grid boundary of each level is larger than or equal to a corresponding coverage rate threshold value and whether the overlapping rate is smaller than or equal to a corresponding overlapping rate threshold value, if yes, the quality inspection is passed, and if no, the grid drawing is refused again;
the version submitting module is used for automatically submitting the version to be used when the submitting time reaches the version submitting expiration date and the version submitting expiration time, or for the user to actively submit the version to be used before the submitting time reaches;
the version auditing module is used for auditing the version to be used, waiting to be released when the auditing is passed, and refusing to re-draw the grid when the auditing is not passed;
the version release module is used for automatically releasing the version to be used when the release time reaches the version release date and the version release time.
Preferably, the grid drawing module comprises a boundary data importing unit, a drawing unit and a matching unit;
the boundary data importing unit is used for importing current boundary data of each level under the grid data system;
the drawing unit is used for drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels, and displaying corresponding grid boundary names in all grid boundaries;
the matching unit is used for carrying out association matching on the grid boundary names of all levels and all grid names under the grid data system, and modifying the grid boundary names to be consistent with the corresponding grid names when the grid boundary names are inconsistent with the associated and matched grid names.
Preferably, the version creation generation module is configured to, when the version update period of the version to be used is a month update period, take the last day of the month as the version release date of the version to be used if the date of the version release date is greater than the value of the last day of the month.
Preferably, the system comprises a version list display module for displaying the version name, the version creation time, the version submission date, the version submission time, the version release date, the version release time and the version state of each version in the form of a list, wherein the version state comprises version drawing, version submitted and version released.
Preferably, the system comprises a version browsing module, wherein the version browsing module is used for users to browse detailed information of each version under each published grid data system.
The invention also provides a method for managing the version of the electronic map in the grid data system, which is characterized by comprising the following steps:
s1, setting a version update period, a version release date and a version release time of each update, a version submission expiration date and a version submission expiration time of each update, and setting a coverage rate threshold and an overlap rate threshold, wherein the version submission expiration date is earlier than the version release date, the coverage rate refers to the total area of each region of a next level under a grid data system in the electronic map, the total area of each region of the next level is overlapped, the area of the region of the last level corresponding to the next level, and the overlap rate refers to the total area of each region of the next level is overlapped, and the area of the region of the last level corresponding to the next level;
s2, creating grid boundaries of polygonal shapes of all levels in the electronic map based on initial boundary data of all levels in a grid data system to form an initial version serving as a base line version and issuing the initial version, wherein the grid boundary of the next level is positioned in the grid boundary of the previous level;
s3, automatically creating and generating a new version to serve as a version to be used based on the version before the new update period starts when the new update period starts, automatically creating and generating the version release date, the version release time, the version submission expiration date and the version submission expiration time of the version to be used based on the version plan, taking the version before the new update period starts as a base line version, and automatically naming the version to be used based on the name of the base line version, wherein the name of the version to be used is editable;
s4, drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels in a grid data system;
s5, detecting whether the coverage rate of the grid boundary of each level is larger than or equal to a corresponding coverage rate threshold value and whether the overlapping rate is smaller than or equal to a corresponding overlapping rate threshold value, if yes, passing the quality inspection, and if no, refusing to carry out grid drawing again; the method comprises the steps of carrying out a first treatment on the surface of the
S6, automatically submitting the version to be used when the submitting time reaches the version submitting expiration date and the version submitting expiration time, or actively submitting the version to be used by the user before the submitting time reaches;
s7, checking the version to be used, waiting to be released when the checking is passed, and refusing to re-draw the grid when the checking is not passed;
and S8, automatically publishing the version to be used when the release time reaches the release date and release time of the version.
Preferably, the step S4 includes the steps of:
s41, importing current boundary data of each level under a grid data system;
s42, drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels, and displaying corresponding grid boundary names in all grid boundaries;
s43, carrying out association matching on the grid boundary names of all the levels and all the grid names under the grid data system, and modifying the grid boundary names to be consistent with the corresponding grid names when the grid boundary names are inconsistent with the associated and matched grid names.
Preferably, in step S3, when the version update period of the version to be used is a month update period, and the date of the version release period is greater than the value of the last date of the month, the last date of the month is taken as the version release date of the version to be used.
Preferably, the method further comprises the steps of:
the version name, version creation time, version submission date, version submission time, version release date, version release time, and version status of each version are displayed in the form of a list, and the version status includes in-version drawing, version submitted, and version released.
Preferably, the method further comprises the steps of: the user can browse the detailed information of each version under each published grid data system.
On the basis of conforming to the common knowledge in the field, the above preferred conditions can be arbitrarily combined to obtain the preferred examples of the invention.
The invention has the positive progress effects that:
the invention makes a version updating plan in advance, and updates the version according to the version updating plan; the electronic map under the drawn grid data system is subjected to quality inspection, submission and auditing operations, and the new version is released when the release time arrives, so that the effective new version electronic map is very accurate. The invention can help the manager of the grid data system to better control the data base of the grid data system, ensure the orderly management of the grid adjustment process, ensure that the grid data is not disordered in the whole life cycle, and effectively support the normal operation of the grid system.
Drawings
Fig. 1 is a block diagram illustrating a system for managing version of an electronic map in a grid data system according to a preferred embodiment of the present invention.
FIG. 2 is a page view of a version schedule set in accordance with a preferred embodiment of the present invention.
FIG. 3 is a page view showing completion of version schedule setting according to the preferred embodiment of the present invention.
FIG. 4 is a page display diagram showing a version list according to a preferred embodiment of the present invention.
Fig. 5 is a flowchart of a method for managing version of an electronic map in a grid data system according to a preferred embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
As shown in fig. 1, the embodiment provides an electronic map version management system in a grid data system, which includes a version plan setting module 1, an initial version creation and release module 2, a version creation and generation module 3, a grid drawing module 4, a grid quality inspection module 5, a version submission module 6, a version auditing module 7, a version release module 8, a version list display module 9 and a version browsing module 10.
The grid data system is a space system, which is an extension of the conventional administrative system (province-city-district/county-town-village), supporting the addition, deletion or modification of hierarchy on the basis of the administrative hierarchy and the creation of corresponding boundaries.
The functions of the respective functional modules are specifically described below:
the version plan setting module 1 is used for setting a version update period, a version release date and a version release time of each update, a version submission expiration date and a version submission expiration time of each update, and a coverage rate threshold and an overlapping rate threshold of the electronic map by a user.
The coverage rate refers to (total area of each region of a next level in a grid data system in the electronic map-total area overlapped among each region of the next level)/area of a region of a previous level corresponding to the next level, and the overlapping rate refers to total area overlapped among each region of the next level/area of a region of the previous level corresponding to the next level.
For example: as shown in fig. 2, the time control and the quality control are set in detail at the set version plan page. In the time control, whether the version release date is selected to be updated weekly or monthly, if the monthly update is selected, the number of the monthly update is selected, if the weekly update is selected, the number of the weekly update is selected, and as the version release date, monday weekly is selected as shown in fig. 3; version release time selects a specific time, as shown in fig. 3, 8, earlier: 00; several days before the release date of the version commit deadline selection version, such as 3 days before the release date of the version commit deadline selection version of fig. 3; version commit deadlines select a particular time, as 8 on fig. 3: 00. in quality control, a coverage threshold and an overlap ratio threshold are set, as in fig. 3, the coverage threshold is set to 99% and the overlap ratio threshold is set to 2%.
The initial version creation and release module 2 is configured to create, in the electronic map, a grid boundary of a polygonal shape of each level based on initial boundary data of each level in the grid data system, so as to form and release an initial version serving as a baseline version, wherein the initial version can pass through without quality inspection or audit, and the grid boundary of the next level is within the grid boundary of the previous level.
For example: the hierarchy under the grid data system is two hierarchies, namely a region and a town, specifically an XX region and an A town, a B town, a C town and a D town below the XX region, a polygonal grid boundary of the XX region is created in the electronic map based on initial boundary data of the XX region, an polygonal grid boundary of the A town is created in the electronic map based on initial boundary data of the A town, a polygonal grid boundary of the B town is created in the electronic map based on initial boundary data of the B town, a polygonal grid boundary of the C town is created in the electronic map based on initial boundary data of the C town, a polygonal grid boundary of the D town is created in the electronic map based on initial boundary data of the D town, initial versions serving as baseline versions are formed by the grid boundaries, and the initial versions can be released without checking. The grid boundaries for the A, B, C and D towns are within the grid boundaries of the XX zone.
The version creation generation module 3 is configured to automatically create and generate a new version as a version to be used based on a version before a new update period starts at the beginning of each new update period, automatically create and generate a version release date, a version release time, a version release expiration date and a version release expiration time of the version to be used based on a version plan, take the version before the beginning of the new update period as a baseline version, and automatically name the version to be used based on the name of the baseline version, where the name of the version to be used is editable.
For example: and (3) carrying out release of the current V1.0 version at 8 A.C. on Monday every week, starting a new update period after release of the current V1.0 version, automatically creating and generating a new version based on the V1.0 version as a version to be used, automatically creating and generating a version release date of the version to be used based on a version plan to be Monday, release time of the version to be used to be 8:00 A.C., release expiration date of the version to be 3 days before release date and release submission expiration time of the version to be 8:00 A.C., and setting the version to be used as a base line version based on the name of the version V1.0.
The version creation generation module 3 is further configured to, when the version update period of the version to be used is a month update period, take the last day of the month as the version release date of the version to be used if the date of the version release date is greater than the value of the last day of the month. For example, the version update period is preset to be a month update period, and the version release date is 30 days of each month, and since only 28 days are 2 months, the version release date of the version to be used is set to be 28 days 2 months.
The grid drawing module 4 is configured to draw a grid boundary of a polygonal shape of each level in the electronic map based on current boundary data of each level in the grid data system, where the grid boundary of the next level is within the grid boundary of the previous level.
The grid drawing module 4 comprises a boundary data importing unit, a drawing unit and a matching unit.
The boundary data importing unit is used for importing current boundary data of each level under the grid data system.
For example: the current boundary data for the A, B, C and D towns below the XX field are imported.
The drawing unit is used for drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels, and displaying corresponding grid boundary names in all grid boundaries.
For example: creating a grid boundary of the polygonal shape of the XX zone in the electronic map based on the current boundary data of the XX zone, creating a grid boundary of the polygonal shape of the A town in the electronic map based on the current boundary data of the A town, creating a grid boundary of the polygonal shape of the B town in the electronic map based on the current boundary data of the B town, creating a grid boundary of the polygonal shape of the C town in the electronic map based on the current boundary data of the C town, and creating a grid boundary of the polygonal shape of the D town in the electronic map based on the current boundary data of the D town.
The matching unit is used for carrying out association matching on the grid boundary names of all levels and all grid names under the grid data system, and modifying the grid boundary names to be consistent with the corresponding grid names when the grid boundary names are inconsistent with the associated and matched grid names.
For example: and performing association matching on a grid boundary name XX (Yangtze) of the XX area (Yang Puou) and a grid name XX area (Yang Puou) under a grid data system, wherein the grid boundary name XX (Yangtze) is inconsistent with the association matching grid name XX area (Yang Puou), and modifying the grid boundary name XX (Yangtze) into a grid boundary name XX area (Yang Puou), so that the A town, the B town, the C town and the D town are pushed.
The grid quality inspection module 5 is used for detecting whether the coverage rate of the grid boundary of each level is greater than or equal to a corresponding coverage rate threshold value, whether the overlapping rate is less than or equal to a corresponding overlapping rate threshold value, if yes, the quality inspection is passed, and if no, the grid drawing is refused again.
For example: coverage of grid boundaries for the ballast level= (total area of a, B, C, and D-total area of overlap between a, B, C, and D)/area of XX zone.
The overlapping ratio of grid boundaries for the ballast level = total area of overlap between a, B, C and D ballast/area of region XX.
If the coverage rate of the grid boundary of the town level is greater than 99% of the coverage rate threshold, the overlapping rate of the grid boundary of the town level is less than 2% of the overlapping rate threshold, the quality inspection is passed, and if the quality inspection is not, the grid drawing is refused again.
The version submitting module 6 is used for automatically submitting the version to be used when the submitting time reaches the version submitting expiration date and the version submitting expiration time, or is used for the user to actively submit the version to be used before the submitting time reaches.
For example: the version to be used is automatically submitted when the submission time reaches the version submission deadline (3 days before every monday) and the version submission deadline (8:00 a.m.), and the user can actively submit the version to be used if the quality inspection is finished before the version submission deadline (3 days before every monday) and the version submission deadline (8:00 a.m.).
The version auditing module 7 is used for enabling a user to manually audit the version to be used, waiting to be released when the audit is passed, and refusing to re-draw the grid when the audit is not passed.
The version release module 8 is configured to automatically release the version to be used when the release time reaches the version release date (e.g. monday) and the version release time (e.g. 8:00 a).
The version list display module 9 is configured to display, in list form, a version name, a version creation time, a version submission date, a version submission time, a version release date, a version release time, and a version status, where the version status includes version submitted and version released in version drawing, see fig. 4.
The version browsing module 10 is configured to allow a user to browse detailed information of each version under each published grid data system.
As shown in fig. 5, the embodiment further provides a method for managing version of an electronic map in a grid data system, which includes the following steps:
step 101, setting a version plan: setting a version update period, a version release date and a version release time of each update, a version submission expiration date and a version submission expiration time of each update, and setting a coverage rate threshold and an overlap rate threshold, wherein the version submission expiration date is earlier than the version release date, the coverage rate refers to the total area of each region of a next level in a grid data system in the electronic map, the total area of each region of the next level, the area of the region of the last level corresponding to the next level, and the overlap rate refers to the total area of each region of the next level, the area of the region of the last level corresponding to the next level.
Step 102, creating a release initial version: based on initial boundary data of each level in a grid data system, grid boundaries of polygonal shapes of each level are created in an electronic map to form an initial version serving as a base line version and released, a version which can pass without quality inspection and auditing is not required, and the grid boundary of the next level is positioned in the grid boundary of the previous level.
Step 103, creating and generating a new version: and automatically creating and generating a new version to be used as a version to be used based on the version before the new update period starts each time, automatically creating and generating the version release date, the version release time, the version submission expiration date and the version submission expiration time of the version to be used based on the version plan, taking the version before the new update period starts as a base line version, and automatically naming the version to be used based on the name of the base line version, wherein the name of the version to be used is editable.
In step 103, when the version update period of the version to be used is a month update period, and the date in the version release date is greater than the value of the last date of the month, the last date of the month is taken as the version release date of the version to be used. For example, the version update period is preset to be a month update period, and the version release date is 30 days of each month, and since only 28 days are 2 months, the version release date of the version to be used is set to be 28 days 2 months.
Step 104, grid boundary drawing: and drawing the grid boundaries of the polygonal shapes of each level in the electronic map based on the current boundary data of each level in the grid data system, wherein the grid boundary of the next level is positioned in the grid boundary of the last level.
Step 104 includes the steps of:
s41, importing current boundary data of each level under a grid data system;
s42, drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels, and displaying corresponding grid boundary names in all grid boundaries;
s43, carrying out association matching on the grid boundary names of all the levels and all the grid names under the grid data system, and modifying the grid boundary names to be consistent with the corresponding grid names when the grid boundary names are inconsistent with the associated and matched grid names.
Step 105, grid boundary quality inspection: and detecting whether the coverage rate of the grid boundary of each level is larger than or equal to a corresponding coverage rate threshold value and whether the overlapping rate is smaller than or equal to a corresponding overlapping rate threshold value, if yes, passing the quality inspection, and if no, refusing to carry out grid drawing again.
Step 106, submitting the new version: and automatically submitting the version to be used when the submitting time reaches the version submitting expiration date and the version submitting expiration time, or actively submitting the version to be used by the user before the submitting time reaches.
Step 107, checking the new version: and checking the version to be used, waiting to be released when the checking is passed, and refusing to re-draw the grid when the checking is not passed.
Step 108, release of new version: and automatically publishing the version to be used when the release time reaches the version release date and the version release time.
Furthermore, the method comprises the following steps:
the version name, version creation time, version submission date, version submission time, version release date, version release time, and version status of each version are displayed in the form of a list, and the version status includes in-version drawing, version submitted, and version released.
The user can browse the detailed information of each version under each published grid data system.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that these are by way of example only, and the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the principles and spirit of the invention, but such changes and modifications fall within the scope of the invention.
Claims (8)
1. The electronic map version management system in the grid data system is characterized by comprising a version plan setting module, an initial version creation and release module, a version creation and generation module, a grid drawing module, a grid quality inspection module, a version submitting module, a version auditing module and a version release module;
the version plan setting module is used for setting a version update period, a version release date and a version release time of each update, a version submission expiration date and a version submission expiration time of each update, and setting a coverage rate threshold and an overlap rate threshold of the electronic map by a user, wherein the version submission expiration date is earlier than the version release date, the coverage rate refers to (total area of each region of a next level in a grid data system in the electronic map-total area of each region of the next level)/area of a region of a last level corresponding to the next level, and the overlap rate refers to total area of each region of the next level overlapped/area of a region of the last level corresponding to the next level;
the initial version creating and issuing module is used for creating grid boundaries of polygonal shapes of all levels in the electronic map based on initial boundary data of all levels in the grid data system so as to form an initial version serving as a base line version and issuing, wherein the grid boundary of the next level is positioned in the grid boundary of the last level;
the version creation generation module is used for automatically creating and generating a new version to be used as a version to be used based on the version before the new update period starts when the new update period starts each time, automatically creating and generating the version release date, the version release time, the version submission expiration date and the version submission expiration time of the version to be used based on the version plan, taking the version before the new update period starts as a base line version, and automatically naming the version to be used based on the name of the base line version, wherein the name of the version to be used is editable;
the grid drawing module is used for drawing the grid boundaries of the polygonal shapes of all the levels in the electronic map based on the current boundary data of all the levels in the grid data system, and entering the grid quality inspection module;
the grid quality inspection module is used for detecting whether the coverage rate of the grid boundary of each level is larger than or equal to a corresponding coverage rate threshold value and whether the overlapping rate is smaller than or equal to a corresponding overlapping rate threshold value, if yes, the quality inspection is passed, the grid quality inspection module is entered, and if no, the grid drawing is refused again, and the grid drawing module is entered;
the version submitting module is used for automatically submitting the version to be used when the submitting time reaches the version submitting expiration date and the version submitting expiration time, or is used for a user to actively submit the version to be used before the submitting time reaches, and enters the version auditing module;
the version auditing module is used for auditing the version to be used, waiting to be released when the auditing is passed, entering the version release module, refusing to re-conduct grid drawing when the auditing is not passed, and entering the grid drawing module;
the version release module is used for automatically releasing the version to be used when the release time reaches the version release date and the version release time;
the grid drawing module comprises a boundary data importing unit, a drawing unit and a matching unit;
the boundary data importing unit is used for importing current boundary data of each level under the grid data system;
the drawing unit is used for drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels, and displaying corresponding grid boundary names in all grid boundaries;
the matching unit is used for carrying out association matching on the grid boundary names of all levels and all grid names under the grid data system, and modifying the grid boundary names to be consistent with the corresponding grid names when the grid boundary names are inconsistent with the associated and matched grid names.
2. The system for managing versions of electronic maps in a grid data system according to claim 1, wherein the version creation generation module is configured to, when a version update period of a version to be used is a month update period, take a last day of a month as a version release date of the version to be used when a date in a version release date is greater than a value of the last day of the month.
3. The system of claim 1, wherein the system includes a version list presentation module for presenting the version name, version creation time, version submission date, version submission time, version release date, version release time, and version status of each version in the form of a list, the version status including in-version, version submitted, and version released.
4. The system for managing versions of an electronic map in a grid data system according to claim 1, wherein the system comprises a version browsing module for a user to browse detailed information of each version in each published grid data system.
5. The electronic map version management method in the grid data system is characterized by comprising the following steps of:
s1, setting a version update period, a version release date and a version release time of each update, a version submission expiration date and a version submission expiration time of each update, and setting a coverage rate threshold and an overlap rate threshold, wherein the version submission expiration date is earlier than the version release date, the coverage rate refers to (total area of each region of a next level-total area overlapping between each region of the next level)/area of a region of the last level corresponding to the next level in a grid data system in the electronic map, and the overlap rate refers to total area of overlapping between each region of the next level/area of a region of the last level corresponding to the next level;
s2, creating grid boundaries of polygonal shapes of all levels in the electronic map based on initial boundary data of all levels in a grid data system to form an initial version serving as a base line version and issuing the initial version, wherein the grid boundary of the next level is positioned in the grid boundary of the previous level;
s3, automatically creating and generating a new version to serve as a version to be used based on the version before the new update period starts when the new update period starts, automatically creating and generating the version release date, the version release time, the version submission expiration date and the version submission expiration time of the version to be used based on the version plan, taking the version before the new update period starts as a base line version, and automatically naming the version to be used based on the name of the base line version, wherein the name of the version to be used is editable;
s4, drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels in a grid data system;
s5, detecting whether the coverage rate of the grid boundary of each level is larger than or equal to a corresponding coverage rate threshold value and whether the overlapping rate is smaller than or equal to a corresponding overlapping rate threshold value, if yes, passing the quality inspection, and if no, refusing to carry out grid drawing again;
s6, automatically submitting the version to be used when the submitting time reaches the version submitting expiration date and the version submitting expiration time, or actively submitting the version to be used by the user before the submitting time reaches;
s7, checking the version to be used, waiting to be released when the checking is passed, and refusing to re-draw the grid when the checking is not passed;
s8, automatically releasing the version to be used when the release time reaches the release date and release time of the version;
step S4 comprises the steps of:
s41, importing current boundary data of each level under a grid data system;
s42, drawing grid boundaries of polygonal shapes of all levels in the electronic map based on current boundary data of all levels, and displaying corresponding grid boundary names in all grid boundaries;
s43, carrying out association matching on the grid boundary names of all the levels and all the grid names under the grid data system, and modifying the grid boundary names to be consistent with the corresponding grid names when the grid boundary names are inconsistent with the associated and matched grid names.
6. The method according to claim 5, wherein in step S3, when the version update period of the version to be used is a month update period, and the date of release of the version is greater than the value of the last date of the month, the last date of the month is taken as the version release date of the version to be used.
7. The method for version management of an electronic map in a grid data system according to claim 5, further comprising the steps of:
the version name, version creation time, version submission date, version submission time, version release date, version release time, and version status of each version are displayed in the form of a list, and the version status includes in-version drawing, version submitted, and version released.
8. The method for version management of an electronic map in a grid data system according to claim 5, further comprising the steps of: the user can browse the detailed information of each version under each published grid data system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111487843.5A CN114153931B (en) | 2021-12-08 | 2021-12-08 | Electronic map version management system and method in grid data system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111487843.5A CN114153931B (en) | 2021-12-08 | 2021-12-08 | Electronic map version management system and method in grid data system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114153931A CN114153931A (en) | 2022-03-08 |
| CN114153931B true CN114153931B (en) | 2024-02-23 |
Family
ID=80453226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111487843.5A Active CN114153931B (en) | 2021-12-08 | 2021-12-08 | Electronic map version management system and method in grid data system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114153931B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101078633A (en) * | 2007-06-12 | 2007-11-28 | 江苏新科数字技术有限公司 | Map data updating method of navigation device |
| CN103578348A (en) * | 2012-08-10 | 2014-02-12 | 袁明千 | Grid method for drawing city map and application thereof |
| CN106250389A (en) * | 2016-07-15 | 2016-12-21 | 西安测绘研究所 | A kind of geographical spatial data method for edition management updated towards dynamic increment |
| CN108897827A (en) * | 2018-06-22 | 2018-11-27 | 北京工商大学 | A kind of highway spatial data automatic update method and system |
| CN109635053A (en) * | 2018-10-31 | 2019-04-16 | 百度在线网络技术（北京）有限公司 | Quality detecting method, device, system and the storage medium of map |
| CN111078239A (en) * | 2018-10-19 | 2020-04-28 | 阿里巴巴集团控股有限公司 | Map data updating method and device |
| CN113607156A (en) * | 2020-09-24 | 2021-11-05 | 深圳市云鼠科技开发有限公司 | Grid map construction method |
-
2021
- 2021-12-08 CN CN202111487843.5A patent/CN114153931B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101078633A (en) * | 2007-06-12 | 2007-11-28 | 江苏新科数字技术有限公司 | Map data updating method of navigation device |
| CN103578348A (en) * | 2012-08-10 | 2014-02-12 | 袁明千 | Grid method for drawing city map and application thereof |
| CN106250389A (en) * | 2016-07-15 | 2016-12-21 | 西安测绘研究所 | A kind of geographical spatial data method for edition management updated towards dynamic increment |
| CN108897827A (en) * | 2018-06-22 | 2018-11-27 | 北京工商大学 | A kind of highway spatial data automatic update method and system |
| CN111078239A (en) * | 2018-10-19 | 2020-04-28 | 阿里巴巴集团控股有限公司 | Map data updating method and device |
| CN109635053A (en) * | 2018-10-31 | 2019-04-16 | 百度在线网络技术（北京）有限公司 | Quality detecting method, device, system and the storage medium of map |
| CN113607156A (en) * | 2020-09-24 | 2021-11-05 | 深圳市云鼠科技开发有限公司 | Grid map construction method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114153931A (en) | 2022-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7349920B1 (en) | Simultaneous display of multiple calendar systems | |
| JP4177280B2 (en) | Planning work management support system and planning work management support program | |
| US7921026B2 (en) | Method and system for generating a timeline associated with a project schedule | |
| US10200468B2 (en) | Active agenda | |
| US7305491B2 (en) | Techniques for handling time zone changes in personal information management software | |
| US20150177952A1 (en) | Computer Method And Apparatus For Automated Scheduling | |
| US8849806B2 (en) | Method, system and apparatus for efficiently determining priority of data in a database | |
| CN104932893B (en) | One kind carrying out event-prompting method and device based on application program | |
| KR20020064924A (en) | A method of organizing and presenting message and deadline information in an electronic calendar system | |
| Chatfield et al. | Microsoft Office Project 2007 Step by Step | |
| WO2009117716A2 (en) | Systems and methods for displaying rolling sequences | |
| CN107193579B (en) | Method and device for realizing planned tasks | |
| CN114153931B (en) | Electronic map version management system and method in grid data system | |
| US20150161571A1 (en) | Calendar Software Interfaces and Methods | |
| JP5824336B2 (en) | Advertisement information management server, advertisement information management system, and advertisement information management program | |
| JP2006202082A (en) | Production line management system, production line management program, recording medium, and method for managing production line | |
| JP2010061603A (en) | Schedule display system | |
| JP2013137764A (en) | Multi-horizon time wheel | |
| CN112132302A (en) | Vehicle reservation processing method and device, electronic equipment and storage medium | |
| US20150302331A1 (en) | Scheduler for athletic facilities | |
| JP2016048519A (en) | Lesson planning support system, lesson planning support program and storage medium | |
| JPH1091681A (en) | Schedule display system | |
| JPH1166151A (en) | Work shift generation support system and recording medium | |
| JP2003316619A (en) | Method for managing deletion schedule file | |
| JP2013137640A (en) | Schedule management device and schedule management method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |