A method for checking the elevation values ​​of connected elevation lines in smart cities

Abstract

This invention specifically relates to a method for checking the elevation values ​​of connected elevation lines applied to smart cities. This method, implemented using ArcGIS, checks the quality of elevation line data by inspecting its field values ​​and outputs any erroneous fields. This method, applied to smart cities, is geared towards data processing and GIS development applications using urban spatial data. It can automate quality checks for different types of elevation line spatial data, improving the efficiency of data quality inspection and data entry, breaking through the bottleneck of existing manual operations, and realizing batch processing of urban spatial data verification and assignment.

Description

Technical Field

[0001] This invention relates to the field of smart city technology, and in particular to a method for checking the elevation values ​​of connected elevation lines in smart cities. Background Technology

[0002] With the continuous development and evolution of spatial data processing technology, spatial data processing is no longer just a technology, but a new development model, a new path for transformation, and a new driving force for profound changes in various industries. As spatial data processing technology is gradually implemented in the industry, it is no longer just an innovative concept and technical solution, but an inevitable path and future choice for the construction and development of new smart cities.

[0003] During the construction and storage of urban basic data, all spatial data needs to undergo quality checks. This is especially true for elevation data, which is frequently used in the military and energy sectors; accurate data is crucial for its effectiveness, and checking the data's field attributes is essential. However, currently, field attribute checks can only be performed manually, which is not only inefficient for urban spatial data processing but also prone to errors. Given the diverse types and large volumes of urban spatial basic data, relying solely on manual processing is far from sufficient to meet current needs.

[0004] To automate the checking and processing of field attributes, this invention proposes a method for checking the elevation values ​​of connected elevation lines in smart cities. Summary of the Invention

[0005] To overcome the shortcomings of existing technologies, this invention provides a simple and efficient method for checking the elevation values ​​of connected elevation lines in smart cities.

[0006] This invention is achieved through the following technical solution:

[0007] A method for checking the elevation values ​​of connected elevation lines applied to smart cities is characterized by: being implemented based on ArcGIS, checking the quality of elevation line data by inspecting the field values ​​of the elevation line data, and outputting the fields with errors;

[0008] Includes the following steps:

[0009] Step S1: Perform batch verification of the elevation line spatial data layer.

[0010] By checking the check items in the configuration file, various types of urban spatial data are checked to find target fields that do not match the source fields. The found fields are recorded, the layers are identified, and the data is stored in the final error file.

[0011] Step S2: Perform format validation on the spatial data fields of the connected elevation lines.

[0012] Spatial data is read using the IGeometryDef, IFeature, IDataset, and IFieldEdit interfaces provided by ArcGIS, and then verified and judged according to the format of the configuration file.

[0013] In step S1, the FeatureWorkspace method is instantiated through the ArcGIS-provided interface IFeatureWorkspace, and the Field method is instantiated through the IFields interface. The Field method is iterated and matched with the fields in the configuration file. After configuration, the field type is judged to determine whether the field type is correct.

[0014] In step S2, the type and length of the field are obtained by instantiating the IGeometryDef interface and using the get_GridSize method in the GeometryDef class. The spatial data is read by instantiating the IFeature interface and using the Store method in the Feature class, and the judgment is made according to the format of the configuration file.

[0015] In step S2, when the urban spatial data contains a dataset, the IDataset interface is used to read the spatial dataset and find the Feature instance to read and verify the fields.

[0016] The data types and data that need to be modified after verification can be modified using methods in the IFieldEdit interface.

[0017] The spatial data includes, but is not limited to, elevation line data, SHP data, MDB data, and GDB data.

[0018] This invention relates to a method for checking the elevation values ​​of connected elevation lines in smart cities. Before processing elevation line data of different data types, the method sets the correspondence between elevation line fields and elevation fields, selects the data type, and sets the name of the elevation line data, the high-level field in the data, the code of the elevation line, and the path of the identifier.

[0019] The implementation process is as follows:

[0020] 1) Select data format

[0021] The data format can be any one of SHP, MDB, or GDB;

[0022] 2) Load elevation data

[0023] Select the elevation line spatial data and load it into the workspace. The data format to be loaded is any one of SHP, MDB or GDB data format.

[0024] 3) Fill in the elevation line name

[0025] Enter the name of the elevation data layer to be processed and the elevation layer name;

[0026] 4) Fill in the elevation field

[0027] Enter the elevation field of the elevation line spatial data; this field is used to determine the elevation value.

[0028] 5) Fill in the elevation line code.

[0029] In the elevation line spatial data, each elevation line data has its own code, and the system designs the codes for various elevation line data.

[0030] 6) Select the error flag file and output folder

[0031] By creating an error identification file, the layer features with errors identified in the annotation verification are selected and corrected, while the spatial data of the elevation lines that have been verified are output.

[0032] A device for checking the elevation values ​​of connected elevation lines applied in smart cities is characterized by comprising a memory and a processor; the memory is used to store a computer program, and the processor is used to execute the computer program to implement the above-described method steps.

[0033] A readable storage medium, characterized in that: a computer program is stored on the readable storage medium, and the computer program, when executed by a processor, implements the above-described method steps.

[0034] The beneficial effects of this invention are: the method for checking the elevation values ​​of connected elevation lines applied to smart cities is designed for data processing and GIS development applications of urban spatial data. It can perform automated quality checks on different types of elevation line spatial data, improve the efficiency of data quality checks and data entry, break through the bottleneck of existing manual operations, and realize batch processing of urban spatial data verification and assignment. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] AppendixFigure 1 This is a schematic diagram of the method for checking the elevation value of connected elevation lines in smart cities, which is based on the present invention. Detailed Implementation

[0037] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions in the embodiments of this invention will be clearly and completely described below in conjunction with the embodiments of this invention. Obviously, the described embodiments are merely some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this invention.

[0038] This method for checking the elevation values ​​of connected elevation lines in smart cities is implemented using ArcGIS. It checks the quality of elevation line data by inspecting the field values ​​of the elevation line data and outputs the fields with errors.

[0039] Includes the following steps:

[0040] Step S1: Perform batch verification of the elevation line spatial data layer.

[0041] By checking the check items in the configuration file, various types of urban spatial data are checked to find target fields that do not match the source fields. The found fields are recorded, the layers are identified, and the data is stored in the final error file.

[0042] Step S2: Perform format validation on the spatial data fields of the connected elevation lines.

[0043] Spatial data is read using the IGeometryDef, IFeature, IDataset, and IFieldEdit interfaces provided by ArcGIS, and then verified and judged according to the format of the configuration file.

[0044] In step S1, the FeatureWorkspace method is instantiated through the ArcGIS-provided interface IFeatureWorkspace, and the Field method is instantiated through the IFields interface. The Field method is iterated and matched with the fields in the configuration file. After configuration, the field type is judged to determine whether the field type is correct.

[0045] In step S2, the type and length of the field are obtained by instantiating the IGeometryDef interface and using the get_GridSize method in the GeometryDef class. The spatial data is read by instantiating the IFeature interface and using the Store method in the Feature class, and the judgment is made according to the format of the configuration file.

[0046] In step S2, when the urban spatial data contains a dataset, the IDataset interface is used to read the spatial dataset and find the Feature instance to read and verify the fields.

[0047] The data types and data that need to be modified after verification can be modified using methods in the IFieldEdit interface.

[0048] The spatial data includes, but is not limited to, elevation line data, SHP data, MDB data, and GDB data.

[0049] This method for checking the elevation values ​​of connected elevation lines applied to smart cities sets up the correspondence between elevation field and elevation field before processing elevation line data of different data types, selects the data type, and sets the name of the elevation line data, the high-level field in the data, the code of the elevation line, and the path of the identifier.

[0050] The method for checking the elevation values ​​of connected elevation lines applied to smart cities is implemented as follows:

[0051] 1) Select data format

[0052] The data format can be any one of SHP, MDB, or GDB;

[0053] The system's "Data Format" selection includes the SHP format, a general spatial data format; the MDB format, which has a certain data volume limit; and the GDB format, which has no data volume limit.

[0054] SHP data format: SHP stands for "ESRIShapeFile", which is a vector graphics format. This format file is mainly used to describe geometric objects (points, polylines and polygons) and can save the position and related attributes of geometric figures.

[0055] ShapeFile refers to a file storage method, which is actually composed of multiple files. Three files are essential to forming a ShapeFile: ".shp", ".shx", and ".dbf". Files representing the same data should have the same filename prefix. For example, storing geometric and attribute data about a lake requires three files: lake.shp, lake.shx, and lake.dbf. The "actual" ShapeFile file has the suffix ".shp," but this single file is incomplete; the other two must be included to form a complete set of geographic data. In addition to these three required files, there are eight optional files that can enhance the expressive power of spatial data. All filenames must conform to the MSDOS 8.3 filename standard (8 characters for the prefix and 3 characters for the suffix, such as shapefile.shp) to maintain compatibility with older applications, although many newer programs support long filenames. Furthermore, all files must be located in the same directory.

[0056] Required files in a ShapeFile:

[0057] .shp — a graphic format used to store the geometric entities of elements;

[0058] .shx — Graphics index format, geometry position index, used to record the position of each geometry in the .shx file, which can speed up the efficiency of searching for a geometry forward or backward;

[0059] .dbf — Attribute data format, storing the attribute data of each geometry in the dBaseIII+ data table format.

[0060] Other optional files:

[0061] .prj — Frame-based, used to store geographic coordinate systems and projection information; it is a text file that stores well-known text projection descriptors.

[0062] .sbnand.sbx — Spatial index of the geometry;

[0063] .fbnand.fbx — Spatial index of the geometry of read-only Shapefiles;

[0064] .ainand.aih — The attribute index of the active field in the list;

[0065] .ixs — A geocoded index for reading and writing Shapefile files;

[0066] .mxs — A geocoded index (ODB format) that can read and write Shapefile files;

[0067] The attribute index of .atx-.dbf files, whose filename format is shapefile.columnname.atx (ArcGIS 8 and later versions);

[0068] .shp.xml — Stores metadata in XML format;

[0069] .cpg — Used to describe the code page of a .dbf file, specifying the character encoding it uses.

[0070] Within each .shp, .shx, and .dbf file, the order of the graphics is consistent. That is, the first record in the .shp file corresponds to the first record in the .shx and .dbf files, and so on. However, the byte order of many fields differs between .shp and .shx files. Therefore, users must handle these byte orders carefully when writing programs to read these file formats. ShapeFile typically uses X and Y coordinates, with X generally corresponding to longitude and Y to latitude; users must pay attention to the X and Y order.

[0071] MDB (Microsoft Database) format is a storage format used by Microsoft Access software. Due to its ease of data manipulation, it is commonly used in some small and medium-sized programs.

[0072] The MDB interface is actually a master-slave serial bus interface operating at a baud rate of 9600. All peripheral devices used (such as coin acceptors, banknote acceptors, card readers, etc.) are slave devices of the master controller (vending machine controller - VMC). The communication method between all peripheral devices and VMC is consistent.

[0073] GDB data format: File Geodatabases have the .gdb extension and are organized as folders. They can store, query, and manage spatial data. They can be expanded and store large amounts of data without using a DBMS. Multiple users can access a File Geodatabase simultaneously, but only one user can edit a single piece of data. Therefore, a File Geodatabase can be accessed by multiple editors, but they must edit different data.

[0074] 2) Load elevation data

[0075] Select the elevation line spatial data and load it into the workspace. The data format to be loaded is any one of SHP, MDB or GDB data format.

[0076] 3) Fill in the elevation line name

[0077] Enter the name of the elevation data layer to be processed and the elevation layer name;

[0078] 4) Fill in the elevation field

[0079] Enter the elevation field of the elevation line spatial data; this field is used to determine the elevation value.

[0080] 5) Fill in the elevation line code.

[0081] In the elevation line spatial data, each elevation line data has its own code, and the system designs the codes for various elevation line data.

[0082] Multiple elevation lines can be set to multiple formats: FCode = '*******', FCode = '*******', where FCode is the encoding field.

[0083] 6) Select the error flag file and output folder

[0084] By creating an error identification file, the layer features with errors identified in the annotation verification are selected and corrected, while the verified elevation line spatial data is output.

[0085] The device for checking the elevation values ​​of connected elevation lines applied in smart cities includes a memory and a processor; the memory is used to store a computer program, and the processor is used to execute the computer program to implement the above-described method steps.

[0086] The readable storage medium stores a computer program that, when executed by a processor, implements the above-described method steps.

[0087] The embodiments described above are merely one specific implementation of the present invention. Ordinary changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for checking the elevation values ​​of connected elevation lines applied in smart cities, characterized in that: Based on ArcGIS, this system checks the quality of elevation line data by inspecting the field values ​​and outputs any erroneous fields. Includes the following steps: Step S1: Perform batch verification of the elevation line spatial data layer. By checking the check items in the configuration file, various types of urban spatial data are checked to find target fields that do not match the source fields. The found fields are recorded, the layers are identified, and the data is stored in the final error file. Step S2: Perform format validation on the spatial data fields of the connected elevation lines. Spatial data is read using the IGeometryDef, IFeature, IDataset, and IFieldEdit interfaces provided by ArcGIS, and then verified and judged according to the format of the configuration file. The type and length of the field are obtained by instantiating the IGeometryDef interface and using the get_GridSize method in the GeometryDef class. The spatial data is read by instantiating the IFeature interface and using the Store method of the Feature class, and the data is judged according to the format of the configuration file. When urban spatial data contains a dataset, use the IDataset interface to read the spatial dataset, find the Feature instance, and perform field reading and verification. The data types and data that need to be modified after verification can be modified using methods in the IFieldEdit interface.

2. The method for checking the elevation value of connected elevation lines applied to smart cities according to claim 1, characterized in that: In step S1, the FeatureWorkspace method is instantiated through the ArcGIS-provided interface IFeatureWorkspace, and the Field method is instantiated through the IFields interface. The Field method is iterated and matched with the fields in the configuration file. After configuration, the field type is judged to determine whether the field type is correct.

3. The method for checking the elevation value of connected elevation lines applied to smart cities according to claim 1, characterized in that: The spatial data includes, but is not limited to, elevation line data, SHP data, MDB data, and GDB data.

4. The method for checking the elevation value of connected elevation lines applied to smart cities according to claim 1, characterized in that: Before processing elevation line data of different data types, set the correspondence between elevation line fields and elevation fields, select the data type, and set the name of the elevation line data, the high-level field in the data, the code of the elevation line, and the path of the identifier.

5. The method for checking the elevation value of connected elevation lines applied to smart cities according to claim 4, characterized in that: The implementation process is as follows: 1) Select data format The data format can be any one of SHP, MDB, or GDB; 2) Load elevation data Select the elevation line spatial data and load it into the workspace. The data format to be loaded is any one of SHP, MDB or GDB data format. 3) Fill in the elevation line name Enter the name of the elevation data layer to be processed and the elevation layer name; 4) Fill in the elevation field Enter the elevation field of the elevation line spatial data; this field is used to determine the elevation value. 5) Fill in the elevation line code. In the elevation line spatial data, each elevation line data has its own code, and the system designs the codes for various elevation line data. 6) Select the error flag file and output folder By creating an error identification file, the layer features with errors identified in the annotation verification are selected and corrected, while the spatial data of the elevation lines that have been verified are output.

6. A device for checking the elevation values ​​of interconnected elevation lines in smart cities, characterized in that: It includes a memory and a processor; the memory is used to store a computer program, and the processor is used to execute the computer program to implement the steps of the method as described in any one of claims 1 to 5.

7. A readable storage medium, characterized in that: The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 5.

Images