Methods, apparatus and readable storage media for style data migration

Abstract

This disclosure relates to the field of map rendering technology, specifically to a style data migration method, apparatus, and readable storage medium. The method includes: acquiring integration version information and corresponding material version information, inputting the referenced material data in the data to be migrated into a material file, acquiring style version information corresponding to the integration version information, inputting the style data in the data to be migrated into a scene file, and generating style material association information. This solution simplifies the structure of the files used to store style data and the files used to store material data after data migration, and unifies the format of the files after data migration, thereby reducing management difficulty and reducing storage space usage.

Description

Technical Field

[0001] This disclosure relates to the field of map rendering technology, specifically to a method, apparatus, and readable storage medium for style data migration. Background Technology

[0002] Electronic maps are digital representations of the real world. Visualized electronic maps (such as...) Figure 1 As shown, maps are typically rendered by a map rendering engine based on map data of the corresponding geographic area. The map rendering engine can be integrated into application software (APP) that requires visualization of electronic maps.

[0003] The inventors of this application have discovered that, with technological advancements, users' demands for the display effects of visualized electronic maps are becoming increasingly diverse and complex. To enable map rendering engines to produce visualized electronic maps with varying effects, existing engines render map data by combining style configuration information (such as color, font, line width, etc.) recorded in map style configuration files with corresponding materials. When map rendering scenarios become complex and diverse, the style configurations also become complex and diverse. How to effectively manage these complex and diverse style configurations has become a problem that needs to be solved by those skilled in the art. Summary of the Invention

[0004] In order to solve the problems in the related technologies, the embodiments of this disclosure are as follows.

[0005] A method, apparatus, and readable storage medium for migrating style data are provided.

[0006] In a first aspect, this disclosure provides a style data migration method, including:

[0007] Obtain the integration version information and the corresponding material version information, and input the material data referenced in the data to be migrated into the material file, wherein the data to be migrated corresponds to the integration version indicated by the integration version information, and the material file corresponds to the material data version indicated by the material version information;

[0008] Obtain the style version information corresponding to the integration version information, and input the style data in the data to be migrated into the scene file, wherein the scene file corresponds to the style data version indicated by the style version information;

[0009] Generate style material association information, which is used to indicate the association between style data version and material data version.

[0010] Secondly, embodiments of this disclosure provide a style data migration apparatus, including:

[0011] The media data migration module is configured to obtain the integration version information and the media version information corresponding to the integration version information, and input the media data referenced in the data to be migrated into the media file, wherein the data to be migrated corresponds to the integration version indicated by the integration version information, and the media file corresponds to the media data version indicated by the media version information;

[0012] The style data migration module is configured to obtain style version information corresponding to the integration version information and input the style data in the data to be migrated into the scene file, wherein the scene file corresponds to the style data version indicated by the style version information;

[0013] The data association module is configured to generate style material association information, which is used to indicate the association between style data version and material data version.

[0014] Thirdly, embodiments of this disclosure provide an electronic device including a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method as described in the first aspect.

[0015] Fourthly, this disclosure provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the method described in the first aspect.

[0016] According to the technical solution provided in this disclosure, by obtaining integration version information and material version information corresponding to the integration version information, and inputting the material data referenced in the data to be migrated into a material file, the corresponding material data is stored in a separate material file corresponding to the material data version; by obtaining style version information corresponding to the integration version information, and inputting the style data in the data to be migrated into a scene file, the corresponding style data is stored in a scene file corresponding to the style data version; and by generating style material association information, it is ensured that the material data version of the material data to be referenced when rendering based on the style data of the corresponding style data version can be known based on the style material association information. In the above scheme, without losing information, the style data and material data in the data to be migrated are migrated to the corresponding scene file and the corresponding material file, respectively. This achieves separate storage of style data and material data. Furthermore, when rendering based on the style data in any scene file, the material data version of the material data referenced by the style data can be obtained based on the material association information generated by the above scheme. This allows the corresponding material file to be read according to the material data version, enabling the material data in the material file to be reused. Therefore, the above scheme simplifies the structure of the files used to store style data and the files used to store material data after data migration, and unifies the format of the files after data migration, thereby reducing the difficulty of management and reducing the occupation of storage space.

[0017] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0018] Other features, objects, and advantages of this disclosure will become more apparent from the following detailed description of non-limiting embodiments, taken in conjunction with the accompanying drawings. In the drawings:

[0019] Figure 1 A schematic diagram of an electronic map according to an embodiment of the present disclosure is shown.

[0020] Figure 2 A schematic flowchart illustrating a pattern data migration method according to an embodiment of the present disclosure is shown.

[0021] Figure 3 A schematic diagram of a display interface for style data in a scene file is shown.

[0022] Figure 4 A schematic flowchart illustrating a pattern data migration method according to an embodiment of the present disclosure is shown.

[0023] Figure 5 A structural block diagram of a pattern data migration apparatus according to an embodiment of the present disclosure is shown.

[0024] Figure 6 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0025] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the method according to embodiments of the present disclosure is shown. Detailed Implementation

[0026] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings to enable those skilled in the art to readily implement them. Furthermore, for clarity, portions unrelated to the description of exemplary embodiments have been omitted from the drawings.

[0027] In this disclosure, it should be understood that terms such as “comprising” or “having” are intended to indicate the presence of features, figures, steps, behaviors, components, parts or combinations thereof disclosed in this specification, and are not intended to exclude the possibility of the presence or addition of one or more other features, figures, steps, behaviors, components, parts or combinations thereof.

[0028] It should also be noted that, unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other. This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0029] In this disclosure, any operation involving the acquisition of user information or user data, or the display of user information or user data to others, is an operation authorized or confirmed by the user, or actively selected by the user.

[0030] The inventors of this application have discovered that, in related technologies, existing map style configuration files generally include style data (i.e., style configuration information) and material data referenced when rendering based on the style data. When the map rendering scene is complex and diverse, the style configuration also becomes complex and diverse, resulting in a relatively complex data structure for the map style configuration file, making it difficult to manage effectively.

[0031] In conclusion, how to effectively manage complex and diverse style configurations has become a problem that needs to be solved by those skilled in the art.

[0032] To address the aforementioned issues, the technical solution disclosed herein involves obtaining integration version information and corresponding material version information, and inputting the referenced material data from the data to be migrated into a material file, thereby storing the corresponding material data through a separate material file corresponding to the material data version; obtaining style version information corresponding to the integration version information, and inputting the style data from the data to be migrated into a scene file, thereby storing the corresponding style data through a scene file corresponding to the style data version; and generating style material association information, thereby ensuring that the material data version of the material data to be referenced when rendering based on the style data of the corresponding style data version can be determined based on the style material association information. In the above scheme, without losing information, the style data and material data in the data to be migrated are migrated to the corresponding scene file and the corresponding material file, respectively. This achieves separate storage of style data and material data. Furthermore, when rendering based on the style data in any scene file, the material data version of the material data referenced by the style data can be obtained based on the material association information generated by the above scheme. This allows the corresponding material file to be read according to the material data version, enabling the material data in the material file to be reused. Therefore, the above scheme simplifies the structure of the files used to store style data and the files used to store material data after data migration, and unifies the format of the files after data migration, thereby reducing the difficulty of management and reducing the occupation of storage space.

[0033] Figure 2 A schematic flowchart illustrating a style data migration method according to an embodiment of the present disclosure is shown. Figure 2 As shown, the style data migration method includes the following steps S101-S104:

[0034] In step S101, the integrated version information and the material version information corresponding to the integrated version information are obtained, and the material data referenced in the data to be migrated is input into the material file.

[0035] Among them, the data to be migrated corresponds to the integration version indicated by the integration version information, and the material files correspond to the material data version indicated by the material version information.

[0036] In step S102, the style version information corresponding to the integration version information is obtained, and the style data in the data to be migrated is input into the scene file.

[0037] The scene file corresponds to the style data version indicated by the style version information.

[0038] In step S103, style material association information is generated.

[0039] Style and material association information is used to indicate the association between style data version and material data version.

[0040] In one implementation of this disclosure, the source files and scene files can be created in advance or created in real time. For example, a data storage container can be created in advance in the data storage unit, that is, at least one scene file and at least one source file can be created, wherein each scene file and each source file can be regarded as a separate data block.

[0041] In one implementation of this disclosure, style data can be understood as data used to indicate the shape, position, and status of various map elements (such as points, lines, surfaces, road signs, buildings, road surfaces, intersections, lanes, etc.) in the corresponding electronic map.

[0042] Material data can be understood as data used to indicate the attributes (such as color, font, font size, icon, icon size, texture, etc.) of various map elements in the corresponding electronic map.

[0043] In one implementation of this disclosure, an integrated version can be understood as a version of the data to be migrated that is instructed to be migrated. Each business line (e.g., main map business line, vertical topic business line, etc.) can correspond to at least one integrated version. The data to be migrated corresponding to each integrated version can include style data and all material data used when rendering the map in at least one map display mode.

[0044] In one implementation of this disclosure, obtaining the integrated version information and the material version information can be understood as reading the pre-stored integrated version information and the material version information, or as obtaining the integrated version information and the material version information input through a human-computer interaction device, or receiving the integrated version information and the material version information sent by other devices or systems.

[0045] In one implementation of this disclosure, obtaining style version information can be understood as reading pre-stored style version information, or as obtaining style version information input through a human-computer interaction device, or receiving style version information sent by other devices or systems.

[0046] It should be noted that, for ease of management, a single source file can include source data with different attributes. Within each attribute, multiple sub-attributes can be included, allowing the source data to be grouped based on these sub-attributes. For example, a source file can include source data with color attributes and source data with texture attributes. For color attributes, this can include layer color attributes corresponding to different layers; similarly, for texture attribute source data, this can include texture dimension sub-attributes and texture type sub-attributes.

[0047] Similarly, the same source file can include style data at different levels (i.e., layer levels), where style data can be grouped according to the level.

[0048] In the technical solution disclosed herein, by obtaining integration version information and material version information corresponding to the integration version information, and inputting the material data referenced in the data to be migrated into a material file, the corresponding material data is stored through a separate material file corresponding to the material data version; by obtaining style version information corresponding to the integration version information, and inputting the style data in the data to be migrated into a scene file, the corresponding style data is stored through a scene file corresponding to the style data version; and by generating style material association information, it is ensured that the material data version of the material data to be referenced when rendering based on the style data of the corresponding style data version can be known based on the style material association information. In the above scheme, without losing information, the style data and material data in the data to be migrated are migrated to the corresponding scene file and the corresponding material file, respectively. This achieves separate storage of style data and material data. Furthermore, when rendering based on the style data in any scene file, the material data version of the material data referenced by the style data can be obtained based on the material association information generated by the above scheme. This allows the corresponding material file to be read according to the material data version, enabling the material data in the material file to be reused. Therefore, the above scheme simplifies the structure of the files used to store style data and the files used to store material data after data migration, and unifies the format of the files after data migration, thereby reducing the difficulty of management and reducing the occupation of storage space.

[0049] In one embodiment of this disclosure, the style data from the data to be migrated is input into a scene file, which can be achieved through the following steps:

[0050] When the style data in the data to be migrated includes style data associated with multiple levels, and the style data associated with any two levels in the multiple levels are the same, the style data corresponding to any level in the multiple levels is input into the scene file, and the style data input into the scene file is associated with multiple levels.

[0051] In one implementation of this disclosure, the style data associated with a hierarchy can be understood as data used to indicate the shape, position, state, and other information of the corresponding map element in the layer at the corresponding hierarchy. The style data may include a hierarchy identifier, which is used to indicate the hierarchy associated with the corresponding style data.

[0052] For example, Figure 3A schematic diagram of a display interface for style data in a scene file is shown. In the style data display interface, corresponding style data can be configured for the corresponding geographic features. This style data is associated with levels 10-22 (map display levels).

[0053] In the technical solution disclosed herein, when the style data in the data to be migrated includes style data associated with multiple levels, and the style data associated with any two levels in the multiple levels are the same, the style data corresponding to any level in the multiple levels is input into the scene file, and the style data input into the scene file is associated with multiple levels. This can minimize the amount of data in the scene file and reduce the occupation of storage space while ensuring that the scene file includes the style data of the corresponding level.

[0054] In one embodiment of this disclosure, before inputting the style data from the data to be migrated into the scene file, the method further includes the following steps:

[0055] Retrieve template information corresponding to the integrated version information. The template information is used to indicate the rendering method based on at least two types of style data.

[0056] Input the data to be migrated into the scenario file, including:

[0057] Generate template rendering data based on the style data and template information in the data to be migrated, and obtain the target format style data based on the template rendering data and the style data in the data to be migrated.

[0058] Input the target format style data into the scene file.

[0059] In one implementation of this disclosure, the method of rendering two types of style data together can be understood as including the specific type of style data, the relative positional relationship of map elements corresponding to different types of style data during rendering, the relative volume relationship of map elements corresponding to different types of style data during rendering, the stacking relationship of map elements corresponding to different types of style data during rendering, the collision relationship of map elements corresponding to different types of style data during rendering, and the relative motion direction and relative motion speed of map elements corresponding to different types of style data during rendering.

[0060] For example, such as Figure 3 As shown, this example illustrates the concept using a scene file containing target format style data corresponding to the default dots in the normal state (levels 10-22). Figure 3 In the interface, template rendering data can be obtained based on the target format style data, and displayed in the "Template Preview" column based on the template rendering data, so that users can see the effect of the default dots in the normal state of 10-22 levels and the two font sizes of "Gaode" text in parallel settings being displayed together.

[0061] In the technical solution disclosed herein, considering that when rendering based on style data, it may be necessary to render based on multiple types of style data simultaneously to achieve a specific rendering effect, template rendering data is generated based on the style data in the data to be migrated and the template information by obtaining the template information corresponding to the integration version information, and target format style data is obtained based on the template rendering data and the style data in the data to be migrated. The target format style data is then input into the scene file, allowing users to obtain template rendering data based on the target format style data in the scene file, so as to display the data through the template rendering data. This allows users to promptly know the rendering effect based on at least two types of style data, thus improving the user experience.

[0062] In one embodiment of this disclosure, the referenced material data in the data to be migrated is input into a material file, including:

[0063] Input the material data of different attributes referenced in each map display mode of the data to be migrated into the material file one by one;

[0064] Input the style data from the data to be migrated into the scene file, including:

[0065] Input the different types of style data for each map display mode in the data to be migrated into the scene file one by one.

[0066] In the technical solution disclosed herein, by inputting the material data of different attributes referenced in each map display mode of the data to be migrated into the material file one by one, and inputting the style data of different types in each map display mode of the data to be migrated into the scene file one by one, the amount of data of the material file and scene file input at one time can be minimized, thereby reducing the system burden and processing costs.

[0067] In one embodiment of this disclosure, the referenced material data in the data to be migrated is input into a material file, including:

[0068] If it is determined that the media file does not store the media data referenced in the data to be migrated, then input the media data referenced in the data to be migrated into the media file.

[0069] In one implementation of this disclosure, determining whether a media file stores media data referenced in the data to be migrated can be understood as comparing the media data in the media file with the media data referenced in the data to be migrated, and determining whether the media file stores the media data referenced in the data to be migrated based on the comparison result. Alternatively, it can be understood as reading a pre-stored media data migration record, or obtaining the media data migration record from another device or system, and determining whether the media file stores the media data referenced in the data to be migrated based on the media data migration record.

[0070] In the technical solution disclosed herein, when it is determined that the material file does not store the material data referenced in the data to be migrated, the material data referenced in the data to be migrated is input into the material file, which can avoid inputting duplicate material data into the material file, thereby improving the efficiency of data processing and reducing the cost of data processing.

[0071] In one embodiment of this disclosure, the referenced material data in the data to be migrated is input into a material file, including:

[0072] Input the referenced material data in the data to be migrated into the material file and generate material mapping information. The material mapping information is used to indicate the correspondence between the integration version and the material data version.

[0073] Generate style material association information, including:

[0074] Generate style material association information based on material mapping information.

[0075] In one implementation of this disclosure, the material mapping information can specifically be a material mapping table, which records the mapping relationship between the integration version and the material data version. Similarly, the style material association information can also specifically be a style material mapping table, which records the mapping relationship between the style data version and the material data version.

[0076] In the technical solution disclosed herein, by inputting the material data referenced in the data to be migrated into the material file and generating material mapping information, and generating style material association information based on the material mapping information, it can be ensured that the corresponding material data is recorded each time it is input into the material file, and style material association information is generated based on the record, thereby improving the reliability of the generated style material association information.

[0077] In one embodiment of this disclosure, before inputting the referenced material data from the data to be migrated into the material file, the method further includes:

[0078] Send a data migration instruction, which must include at least the integration version information;

[0079] Receive the data to be migrated. The data to be migrated is the data migration instruction sent by the corresponding platform.

[0080] In one implementation of this disclosure, sending a data migration instruction can be understood as sending the instruction to the corresponding data interface of the corresponding platform based on a preset communication protocol (such as Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS)). In addition to integration version information, this data migration instruction can also be used to indicate more granular compositional information of the data to be migrated, such as the type of style data and the attributes of material data within the data to be migrated.

[0081] In the technical solution disclosed herein, by sending a data migration instruction that includes at least integration version information and receiving the data to be migrated from the corresponding platform in response to the data migration instruction, it is convenient for users to obtain the data to be migrated from the corresponding platform, thereby improving the user experience.

[0082] In one embodiment of this disclosure, the method further includes the following steps:

[0083] Generate a pre-migration release file based on the data to be migrated, and generate a post-migration release file based on the scene file and material file;

[0084] Match based on the files released before and after the migration;

[0085] When the files published before and after migration do not match, re-enter the referenced material data from the data to be migrated into the material file, and / or re-enter the style data from the data to be migrated into the scene file.

[0086] In one implementation of this disclosure, the pre-migration release file and the post-migration release file can be understood as files that can be directly used by clients with electronic map display capabilities (such as clients equipped with navigation software) to render on electronic maps.

[0087] In one implementation of this disclosure, when the pre-migration release file and the post-migration release file do not match, further analysis can be performed on the specific parts of the pre-migration release file and the post-migration release file that do not match. Based on the analysis results, the parts of the material files that need to be re-entered in the material data referenced in the data to be migrated can be determined and re-entered. And / or, based on the analysis results, the parts of the scene files that need to be re-entered in the style data in the data to be migrated can be determined and re-entered.

[0088] In one implementation of this disclosure, a pre-migration release file is generated based on the data to be migrated, and a post-migration release file is generated based on the scene file and the material file; the pre-migration release file and the post-migration release file are matched; when the pre-migration release file and the post-migration release file do not match, the material data referenced in the data to be migrated is re-inputted into the material file, and / or the style data in the data to be migrated is re-inputted into the scene file, which can improve the accuracy of the data in the material file and / or scene file after data migration.

[0089] Figure 4 A schematic flowchart illustrating a style data migration method according to an embodiment of the present disclosure is shown. Figure 4 As shown, the style data migration method includes the following steps:

[0090] In step S201, the integrated version information and the material version information corresponding to the integrated version information are obtained.

[0091] In step S202, a data migration instruction is sent.

[0092] In step S203, the data to be migrated is received.

[0093] In step S204, when it is determined that the material file does not store the material data referenced in the data to be migrated, the material data of different attributes referenced in each map display mode of the data to be migrated are input into the material file one by one, and material mapping information is generated.

[0094] In step S205, style version information and template information corresponding to the integrated version information are obtained.

[0095] In step S206, template rendering data is generated based on the style data and template information in the data to be migrated, and target format style data is obtained based on the template rendering data and the style data in the data to be migrated.

[0096] In step S207, when the target format style data includes style data associated with each of the multiple levels, and the style data associated with any two levels in the multiple levels are the same, the different types of style data in each map display mode of the target format style data corresponding to any level in the multiple levels are input into the scene file one by one, and the target format style data input into the scene file is associated with the multiple levels.

[0097] In step S208, style material association information is generated based on the material mapping information.

[0098] In step S209, a pre-migration release file is generated based on the data to be migrated, and a post-migration release file is generated based on the scene file and the material file.

[0099] In step S210, matching is performed based on the pre-migration release file and the post-migration release file;

[0100] In step S211, when the pre-migration release file and the post-migration release file do not match, the referenced material data in the data to be migrated is re-entered into the material file, and / or, the style data in the data to be migrated is re-entered into the scene file.

[0101] Figure 5 A structural block diagram of a pattern data migration apparatus according to an embodiment of the present disclosure is shown. This apparatus can be implemented as part or all of an electronic device through software, hardware, or a combination of both.

[0102] like Figure 5 As shown, the style data migration device 300 includes:

[0103] The material data migration module 301 is configured to obtain the integration version information and the material version information corresponding to the integration version information, and input the material data referenced in the data to be migrated into the material file, wherein the data to be migrated corresponds to the integration version indicated by the integration version information, and the material file corresponds to the material data version indicated by the material version information.

[0104] The style data migration module 302 is configured to obtain style version information corresponding to the integration version information and input the style data in the data to be migrated into the scene file, wherein the scene file corresponds to the style data version indicated by the style version information;

[0105] The data association module 303 is configured to generate style material association information, which is used to indicate the association between style data version and material data version.

[0106] According to the technical solution provided in this disclosure, by obtaining integration version information and material version information corresponding to the integration version information, and inputting the material data referenced in the data to be migrated into a material file, the corresponding material data is stored in a separate material file corresponding to the material data version; by obtaining style version information corresponding to the integration version information, and inputting the style data in the data to be migrated into a scene file, the corresponding style data is stored in a scene file corresponding to the style data version; and by generating style material association information, it is ensured that the material data version of the material data to be referenced when rendering based on the style data of the corresponding style data version can be known based on the style material association information. In the above scheme, without losing information, the style data and material data in the data to be migrated are migrated to the corresponding scene file and the corresponding material file, respectively. This achieves separate storage of style data and material data. Furthermore, when rendering based on the style data in any scene file, the material data version of the material data referenced by the style data can be obtained based on the material association information generated by the above scheme. This allows the corresponding material file to be read according to the material data version, enabling the material data in the material file to be reused. Therefore, the above scheme simplifies the structure of the files used to store style data and the files used to store material data after data migration, and unifies the format of the files after data migration, thereby reducing the difficulty of management and reducing the occupation of storage space.

[0107] This disclosure also discloses an electronic device. Figure 6 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Figure 6 As shown, the electronic device includes a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method according to embodiments of the present disclosure.

[0108] This disclosure provides a style data migration method, including:

[0109] Obtain the integration version information and the corresponding material version information, and input the material data referenced in the data to be migrated into the material file, wherein the data to be migrated corresponds to the integration version indicated by the integration version information, and the material file corresponds to the material data version indicated by the material version information;

[0110] Obtain the style version information corresponding to the integration version information, and input the style data in the data to be migrated into the scene file, wherein the scene file corresponds to the style data version indicated by the style version information;

[0111] Generate style material association information, which is used to indicate the association between style data version and material data version.

[0112] In one embodiment of this disclosure, the style data in the data to be migrated is input into a scene file, including:

[0113] When the style data in the data to be migrated includes style data associated with multiple levels, and the style data associated with any two levels in the multiple levels are the same, the style data corresponding to any level in the multiple levels is input into the scene file, and the style data input into the scene file is associated with multiple levels.

[0114] In one embodiment of this disclosure, before inputting the style data from the data to be migrated into the scene file, the method further includes:

[0115] Retrieve template information corresponding to the integrated version information. The template information is used to indicate the rendering method based on at least two types of style data.

[0116] Input the data to be migrated into the scenario file, including:

[0117] Generate template rendering data based on the style data and template information in the data to be migrated, and obtain the target format style data based on the template rendering data and the style data in the data to be migrated.

[0118] Input the target format style data into the scene file.

[0119] In one embodiment of this disclosure, the referenced material data in the data to be migrated is input into a material file, including:

[0120] Input the material data of different attributes referenced in each map display mode of the data to be migrated into the material file one by one;

[0121] Input the style data from the data to be migrated into the scene file, including:

[0122] Input the different types of style data for each map display mode in the data to be migrated into the scene file one by one.

[0123] In one embodiment of this disclosure, the referenced material data in the data to be migrated is input into a material file, including:

[0124] If it is determined that the media file does not store the media data referenced in the data to be migrated, then input the media data referenced in the data to be migrated into the media file.

[0125] In one embodiment of this disclosure, the referenced material data in the data to be migrated is input into a material file, including:

[0126] Input the referenced material data in the data to be migrated into the material file and generate material mapping information. The material mapping information is used to indicate the correspondence between the integration version and the material data version.

[0127] Generate style material association information, including:

[0128] Generate style material association information based on material mapping information.

[0129] In one embodiment of this disclosure, before inputting the referenced material data from the data to be migrated into the material file, the method further includes:

[0130] Send a data migration instruction, which must include at least the integration version information;

[0131] Receive the data to be migrated. The data to be migrated is the data migration instruction sent by the corresponding platform.

[0132] In one embodiment of this disclosure, the method further includes:

[0133] Generate a pre-migration release file based on the data to be migrated, and generate a post-migration release file based on the scene file and material file;

[0134] Match based on the files released before and after the migration;

[0135] When the files published before and after migration do not match, re-enter the referenced material data from the data to be migrated into the material file, and / or re-enter the style data from the data to be migrated into the scene file.

[0136] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the method according to embodiments of the present disclosure is shown.

[0137] like Figure 7 As shown, the computer system includes a processing unit that can execute various methods described above based on a program stored in a read-only memory (ROM) or a program loaded from a storage portion into a random access memory (RAM). The RAM also stores various programs and data required for the operation of the computer system. The processing unit, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0138] The following components are connected to the I / O interface: input sections including keyboards, mice, etc.; output sections including cathode ray tubes (CRTs), liquid crystal displays (LCDs), and speakers; storage sections including hard disks, etc.; and communication sections including network interface cards such as LAN cards and modems. The communication section performs communication processes via a network such as the Internet. Drives are also connected to the I / O interface as needed. Removable media, such as disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive as needed so that computer programs read from them can be installed into the storage section as needed. The processing unit can be implemented as a CPU, GPU, TPU, FPGA, NPU, etc.

[0139] In particular, according to embodiments of this disclosure, the methods described above can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing program code for performing the methods described above. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium.

[0140] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0141] The units or modules described in the embodiments of this disclosure can be implemented in software or programmable hardware. The described units or modules can also be located in a processor, and the names of these units or modules do not necessarily constitute a limitation on the unit or module itself.

[0142] In another aspect, this disclosure also provides a computer-readable storage medium, which may be a computer-readable storage medium included in the electronic device or computer system described above; or it may be a standalone computer-readable storage medium not assembled into a device. The computer-readable storage medium stores one or more programs, which are used by one or more processors to perform the methods described in this disclosure.

[0143] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

Claims

1. A style data migration method, comprising: obtaining integration version information and material version information corresponding to the integration version information, and inputting material data referenced in to-be-migrated data into a material file, wherein the to-be-migrated data corresponds to an integration version indicated by the integration version information, and the material file corresponds to a material data version indicated by the material version information; obtaining style version information corresponding to the integration version information, and inputting style data in the to-be-migrated data into a scene file, wherein the scene file corresponds to a style data version indicated by the style version information; generating style-material association information, the style-material association information being used to indicate an association between the style data version and the material data version.

2. The schema data migration method of claim 1, wherein, The inputting of the style data in the to-be-migrated data into the scene file comprises: when the style data in the to-be-migrated data comprises style data respectively associated with a plurality of levels and the style data respectively associated with any two levels of the plurality of levels is the same, inputting the style data corresponding to any level of the plurality of levels into the scene file, and associating the style data input into the scene file with the plurality of levels.

3. The schema data migration method of claim 1, wherein, Before the inputting of the style data in the to-be-migrated data into the scene file, the method further comprises: obtaining template information corresponding to the integration version information, the template information being used to indicate a manner of rendering according to at least two types of style data together; The inputting of the to-be-migrated data into the scene file comprises: generating template rendering data according to the style data in the to-be-migrated data and the template information, and obtaining target format style data according to the template rendering data and the style data in the to-be-migrated data; inputting the target format style data into the scene file.

4. The style data migration method of any of claims 1-3, wherein, The inputting of the material data referenced in the to-be-migrated data into the material file comprises: inputting material data of different attributes referenced in each map display mode of the to-be-migrated data into the material file one by one; The inputting of the style data in the to-be-migrated data into the scene file comprises: inputting different types of style data in each map display mode of the to-be-migrated data into the scene file one by one.

5. The style data migration method of any of claims 1-3, wherein, The inputting of the material data referenced in the to-be-migrated data into the material file comprises: when it is determined that the material data referenced in the to-be-migrated data is not stored in the material file, inputting the material data referenced in the to-be-migrated data into the material file.

6. The style data migration method of any one of claims 1-3, wherein, The inputting of the material data referenced in the to-be-migrated data into the material file comprises: inputting the material data referenced in the to-be-migrated data into the material file, and generating material mapping information, the material mapping information being used to indicate a correspondence between the integration version and the material data version; The generation of the style-material association information comprises: generating the style-material association information according to the material mapping information.

7. The style data migration method of any of claims 1-3, wherein, Before the inputting of the material data referenced in the to-be-migrated data into the material file, the method further comprises: sending a data migration instruction, the data migration instruction at least comprising the integration version information; receiving the data to be migrated, the data to be migrated being sent by a corresponding platform in response to the data migration instruction.

8. The style data migration method of any of claims 1-3, wherein, The method further comprises: generating a pre-migration release file according to the data to be migrated, and generating a post-migration release file according to the scene file and the material file; matching the pre-migration release file and the post-migration release file; when the pre-migration release file and the post-migration release file do not match, re-inputting material data referenced in the data to be migrated into the material file, and / or re-inputting style data in the data to be migrated into the scene file.

9. A style data migration apparatus, comprising: a material data migration module configured to acquire integration version information and material version information corresponding to the integration version information, and to input material data referenced in data to be migrated into a material file, wherein the data to be migrated corresponds to an integration version indicated by the integration version information, and the material file corresponds to a material data version indicated by the material version information; a style data migration module configured to acquire style version information corresponding to the integration version information, and to input style data in the data to be migrated into a scene file, wherein the scene file corresponds to a style data version indicated by the style version information; a data association module configured to generate style-material association information, the style-material association information being used to indicate that the style data version is associated with the material data version.

10. A computer readable storage medium having stored thereon computer instructions, wherein, The computer instructions, when executed by a processor, implement the method steps of any one of claims 1-8.

Images