Intelligent general drawing auxiliary layout method and system based on module calling and automatic verification

Abstract

The invention provides an intelligent general drawing auxiliary layout method and system based on module calling and automatic verification, and is applied to the field of data processing application. According to the application, module calling and preprocessing are performed on basic data, a space module library G1 module is called in a one-key manner, data circulation from G1 to G3 is realized, and static spacing data, sunlight bar shadow graph data, a building number interval value, unit assembly basic data, a building-level house type index and a general graph-level business state index are generated based on a multi-city rule billboard; processing the static spacing data, the sunlight bar shadow graph data, the building number interval value, the unit assembly basic data, the building-level house type index and the general graph-level business state index to generate a compliance verification result; processing the compliance verification result to generate potential problem scheme information; and processing the potential problem scheme information based on the feature dimension to generate intelligent general graph auxiliary layout abnormal information.

Description

Technical Field

[0001] The present invention relates to the field of data processing applications, and in particular to an intelligent master map auxiliary arrangement method and system based on module calling and automatic verification. Background Art

[0002] The master plan (or master plan) represents the overall layout of a building site. The existing manual process for drawing is inefficient. The traditional process relies on manual calculations of metrics like sunlight exposure, spacing, and volume ratio, taking up to 46.4 hours (for a 150,000 square meter project, for example). This process also requires repeated adjustments, resulting in low efficiency and prone to errors. Manual verification of rules (such as sunlight exposure, spacing, and business type ratios) relies on experience and lacks automated tool support, leading to a high risk of errors and omissions.

[0003] Data flow and collaboration are hindered by barriers. Metric analysis must be completed manually, hindering integration with upstream and downstream systems. This creates significant data silos between functions and increases collaboration costs. Multi-city rule adaptation relies on manual queries and lacks real-time dynamic verification, making it difficult to meet differentiated planning requirements across regions. Visualization and decision support are insufficient, with a lack of intuitive compliance visualization tools (such as dynamic sunlight and shadow simulation and business color annotation). Problem identification relies on manual troubleshooting, which takes a long time.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore includes information that does not constitute prior art known to ordinary technicians in this field. Summary of the Invention

[0005] This application aims to provide an intelligent master plan auxiliary layout method and system based on module invocation and automatic verification, which, at least to a certain extent, overcomes the problems of existing technologies. By acquiring basic data, the G1 module can be invoked with one click to generate multiple types of data. After processing, compliance verification results, information on potential problem solutions, and exception information are generated. The system can automatically calculate sunlight spacing, fire protection spacing, and other parameters, achieve multi-city rule adaptation, and automatically analyze indicators and provide visual output.

[0006] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by practice of the invention.

[0007] According to one aspect of the present application, a method for intelligent master plan auxiliary arrangement based on module calling and automatic verification is provided, including: obtaining basic data for intelligent master plan auxiliary arrangement, wherein the basic data includes project initialization information, spatial module library G1 module data, multi-city rule board data, manually arranged master plan scheme and indicator data; performing module calling and preprocessing on the basic data, calling the spatial module library G1 module with one click, realizing data flow from G1 to G3, generating static spacing data, sunshine stick shadow map data, and building number interval based on the multi-city rule board Values, basic data for unit assembly, building-level household type indicators and general plan-level business indicators; process static spacing data, sunshine stick shadow map data, building quantity interval values, basic data for unit assembly, building-level household type indicators and general plan-level business indicators to generate compliance verification results; process the compliance verification results to generate potential problem solution information; process the potential problem solution information based on feature dimensions to generate intelligent general plan auxiliary layout exception information, where the intelligent general plan auxiliary layout exception information includes solution-level exception reports, visual tags, and data flow logs.

[0008] Another aspect of the present application is an intelligent master plan auxiliary layout device based on module calling and automatic verification, characterized in that it includes: an acquisition module for acquiring basic data for intelligent master plan auxiliary layout; a processing module for performing module calling and preprocessing on the basic data, calling the spatial module library G1 module with one click to realize the data flow from G1 to G3, and generating static spacing data, sunshine stick shadow map data, building number interval value, unit assembly basic data, building-level apartment type indicators and master plan level business type indicators based on multi-city rule dashboards; processing the static spacing data, sunshine stick shadow map data, building number interval value, unit assembly basic data, building-level apartment type indicators and master plan level business type indicators to generate compliance verification results; processing the compliance verification results to generate potential problem solution information; processing the potential problem solution information based on feature dimensions to generate intelligent master plan auxiliary layout exception information.

[0009] According to another aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a second processor, the above-mentioned intelligent master map auxiliary arrangement method based on module calling and automatic verification is implemented.

[0010] This application provides an intelligent master plan auxiliary layout method and system based on module calling and automatic verification. The server obtains basic data and calls the G1 module with one click to generate multiple types of data. After processing, it generates compliance verification results, potential problem solution information and abnormal information. The system can automatically calculate sunlight spacing, fire protection spacing, etc., realize multi-city rule adaptation, automatically analyze indicators and visualize output. Actual measurements show that the time for young architects to arrange the master plan has been reduced from 46.4 hours to 13 hours, an efficiency increase of 70%, significantly reducing manual errors, improving layout efficiency and compliance, and providing an efficient tool for intelligent master plan design.

[0011] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 A flowchart of an intelligent master map auxiliary arrangement method based on module calling and automatic verification provided by an embodiment of the present application is shown;

[0013] Figure 2 A structural diagram of an intelligent master map auxiliary arrangement device based on module calling and automatic verification provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0014] The preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0015] The following combination Figure 1 To describe the intelligent master map auxiliary arrangement method based on module calling and automatic verification according to the exemplary embodiment of the present application. In one embodiment, the present application also proposes an intelligent master map auxiliary arrangement method and system based on module calling and automatic verification. Figure 1 Shown, including:

[0016] S101, obtaining basic data for intelligent general map auxiliary arrangement.

[0017] In one embodiment, basic data includes project initialization information, spatial module library G1 module data, multi-city rule dashboard data, manually arranged master plan, and indicator data. Project initialization information refers to the basic planning data used during the project launch phase, which determines the basic framework for the master plan design. For example, consider site mapping rules: A residential project located in Pudong New Area, Shanghai, uses the Shanghai Urban Construction Coordinate System, a 1:500 scale, and the Wusong elevation system. Product positioning: The design brief requires a "floor area ratio ≤ 2.5, a greening ratio ≥ 35%, and the primary residential unit type is 80-120 square meters, meeting basic needs, with a proportion of ≥ 70%." Planning conditions: A land area of ​​50,000 square meters, a building height limit of 80 meters, and setback requirements of "the main building must be ≥ 3 meters from the site boundary and ≥ 5 meters from the south road edge." Design brief parameters: A 9-class kindergarten (building area ≥ 3,000 square meters) and community commercial facilities (accounting for ≤ 15%) are required.

[0018] The G1 module stores standardized product module data for quick call generation of building basic models. For example, standard unit data: Unit A: 80㎡, two bedrooms and one living room, standard floor outline dimensions are 12m×50m, including balcony (area 8㎡, overlap deduction rate 50%). Unit B: 120㎡, three bedrooms and two living rooms, standard floor outline dimensions are 14m×50m, and public corridor area is 15㎡ (full deduction). The built-in rule algorithms include the following: Sunshine calculation rules: In Shanghai, the sunshine on the Great Cold Day is ≥2 hours, the calculation model adopts the "degree day method", and the solar altitude angle algorithm is based on the local latitude (31°14′N). Spacing calculation rules: The spacing coefficient of high-rise residential buildings is 1.3 (i.e. building height × 1.3), and the spacing of multi-story residential buildings is ≥6 meters.

[0019] The multi-city rule dashboard data is a database that integrates the planning rules of various cities and is used to automatically match the compliance requirements of the project location. For example, the Shanghai rules include the following: Sunlight standards: ≥2 hours of sunshine on the Great Cold Day for residential buildings, and ≥3 hours on the Winter Solstice for kindergartens. Business format ratio: The commercial area accounts for ≤10%, and the supporting facilities area must meet 150 square meters per thousand people. Setback rules: High-rise buildings must set back ≥5 meters from the land red line, and multi-story buildings must ≥3 meters. The Beijing rules are as follows: Floor area ratio calculation rules: Underground building area is not included in the floor area ratio, but the commercial area ratio is capped at 1.5. Unit type ratio: Units with an area of ​​less than 70 square meters in affordable housing account for ≥50%.

[0020] The master plan and index data for the manually arranged site are the preliminary plans and derived indicators manually created by the designer, serving as the input for automated processing. For example, the master plan proposes 10 high-rise residential buildings (18-26 stories) arranged along the site's boundary line, with landscaped green spaces in between. Commercial facilities are concentrated on the east side of the site, and the kindergarten is located in the northwest corner, 50 meters from the road.

[0021] The metrics are as follows: Building-level metrics: Building 1# includes 20 units of Unit A and 10 units of Unit B, with a total floor area of ​​26,000 square meters and an occupancy rate of 82%. Master plan-level metrics: Total construction area of ​​125,000 square meters, a floor area ratio of 2.5, a greening rate of 36%, and commercial area of ​​18,000 square meters (accounting for 14.4%). Manual annotation: The designer noted, "The distance between Building 3# and the south building is measured to be 30 meters. Verification is required to ensure that it meets the sunlight requirements."

[0022] The designer uploads the project initialization information (such as the land red line map and design task book of a project in Shanghai) through the intelligent master plan platform, and the system automatically retrieves the Shanghai standard unit (80㎡ / 120㎡ apartment type) in the G1 module and the Shanghai rules in the multi-city rule dashboard. Based on the manual layout plan, the system automatically calculates the sunlight spacing (such as the height of Building 3# is 60 meters, the spacing is 30 meters, the spacing coefficient = 30 / 60 = 0.5 < 1.3, triggering a red alert). According to the unit assembly results, the building-level apartment indicators (such as the proportion of just-needed apartments is 75%) and the master plan-level business indicators (commercial accounts for 14.4%, which is compliant) are automatically analyzed. Through standardized data acquisition processes, manual input errors are reduced, and a verifiable initial plan is quickly generated, providing a basis for subsequent automated layout and compliance verification.

[0023] S102, perform module call and preprocessing on basic data, call the spatial module library G1 module with one click, realize the data flow from G1 to G3, and generate static spacing data, sunshine stick shadow map data, building quantity interval value, unit assembly basic data, building-level apartment indicators and master map-level business indicators based on multi-city rule dashboards.

[0024] In one implementation, based on the sunlight calculation rules and fire separation standard data built into the spatial module library G1 module, as well as city-specific spacing parameters extracted from the multi-city rule dashboard, combined with site terrain data, building coordinates, and orientation data, a geometric algorithm is used to calculate the minimum sunlight separation and fire separation values ​​between buildings, thereby generating static separation data. For a residential project in Shanghai, the land is 300 meters long from north to south and 200 meters wide from east to west. The buildings face due south, and the site is flat with no terrain elevation differences. The G1 module's built-in rules state that the sunlight separation coefficient for high-rise residential buildings in Shanghai is 1.3, and the fire separation distance is ≥13 meters (between high-rise buildings). Multi-city rule dashboard parameters: setback distance ≥5 meters (land boundary), ≥3 meters (road edge). Site data: building coordinates (origin coordinates X=1000, Y=2000), building 1 height 60 meters (20 floors), building 2 height 50 meters (17 floors), the two buildings are arranged north-south, and the measured separation is 30 meters.

[0025] The calculation process of sunlight spacing is as follows: 60 meters × 1.3 = 78 meters (standard value), the actual measurement is 30 meters < 78 meters, and the deviation rate is -61.5% (red alert). Fire separation distance verification: the actual measurement is 30 meters ≥ 13 meters, which is compliant. Setback verification: Building 1 is 8 meters ≥ 5 meters away from the south land red line, which is compliant; 6 meters ≥ 3 meters away from the north road edge, which is compliant. The static spacing data is a sunlight spacing of 30 meters (standard 78 meters), a fire separation distance of 30 meters, a setback distance (8 meters south / 6 meters north), and a height limit of 80 meters (not exceeded).

[0026] Based on the geographic coordinate data of the site, the building orientation is generated in combination with the building orientation data. In this residential project in Shanghai, the specific geographical environment and meteorological conditions have a profound impact on the sunlight conditions of the building. On the winter solstice, the sun's altitude angle is 35° and the azimuth angle is 150° (30° west of due south). These data are the key starting parameters for sunlight simulation. From the perspective of generating the building orientation, relying on the established coordinate system of the site and combining the south-facing orientation of the building, according to the general azimuth definition rules (due north is 0° and due south is 180°), the azimuth angle of the building in this project can be accurately determined to be 0°. This orientation information plays an important role as a positioning benchmark in the subsequent sunlight simulation process. It is the basis for accurately simulating the relationship between the angle of sunlight and the relative position of the building.

[0027] The G1 module uses a building model that shows the temporal variations of solar altitude and azimuth angles, along with local sunlight standard data from the multi-city rule board. By simulating the angle and position of sunlight on the building model at different time periods, a graphics rendering algorithm is used to generate data on the solar shadow range for each building at different time periods, creating a sunlight stick figure. The sunlight simulation utilizes the advanced solar trajectory model in the G1 module, a multi-parameter dynamic model based on astronomical principles. Its internal structure comprises multiple layers. The core layer simulates the annual apparent motion of the sun, accounting for the elliptical nature of the Earth's orbit around the sun and the seasonal variations caused by the Earth's axial tilt. The middle layer performs detailed calculations of the continuous temporal variations of the daily solar altitude and azimuth angles. The outer layer incorporates geographic parameters such as the project's latitude and longitude to achieve precise local adaptation. Key parameters in the model include time (accurate to the hour), date, local longitude, and local latitude. For this simulation, the simulation period was set between 8:00 AM and 4:00 PM to fully demonstrate the effects of sunlight on the building during this period.

[0028] At 8:00 AM, based on trigonometric calculations, the length of Building 1's shadow was calculated by multiplying the building's height (60 meters) by tan(35°), resulting in a value of approximately 85.7 meters. Based on the actual building layout and floor heights, this shadow extended to the bottom three floors of Building 2. This calculation accurately reflects the low solar altitude at that time, resulting in longer shadows due to oblique sunlight.

[0029] 12:00 PM is the time of day when the sun's altitude is at its highest. At this time, the shadow of Building 1 is at its shortest, approximately 42 meters, according to model calculations, covering only the bottom floor of Building 2. This reflects the characteristic of midday when the sun's rays are almost direct and shadows are significantly shorter.

[0030] At 16:00, the sun's position is symmetrical to that at 8:00, so the length of the shadow of Building 1# is also about 85.7 meters, again covering the bottom three floors of Building 2#, demonstrating the symmetry of the sun's movement trajectory.

[0031] In terms of calculating sunshine duration, the team focused on the south-facing windows on the first floor of Building 2. By analyzing and accumulating sunlight exposure at different times, the team concluded that the window received 1.5 hours of sunshine during the simulated period. However, according to the Shanghai region's Great Cold Day standard, residential buildings must meet a sunshine duration requirement of ≥ 2 hours. This window clearly failed to meet this requirement, triggering a yellow alert, prompting the design team to optimize the building's layout, spacing, or orientation. The resulting sunshine stick shadow map data detailed the shadows cast on floors 1-3 of Building 2 during the 8:00-10:00 and 14:00-16:00 periods, with a cumulative sunshine deficiency period of 1 hour. These data, presented in intuitive graphics with precise time period annotations, provided a key basis for the project's subsequent sunshine optimization design, enabling the design team to specifically improve the building's sunlight conditions, enhancing living comfort and regulatory compliance.

[0032] Obtain land area data from the project initialization information, and unit area data and standard floor plan data from the G1 module of the spatial module library. The project site is a rectangular plot, 300 meters long from north to south and 166.67 meters wide from east to west, with a total area of ​​50,000 square meters (300 x 166.67). The planning requirement is a floor area ratio of ≤ 2.5, meaning the maximum total building area = 50,000 x 2.5 = 125,000 square meters.

[0033] The design brief parameters are as follows: Main apartment types: 80 square meters, two bedrooms and one living room (basic needs, accounting for 70%), and 120 square meters, three bedrooms and two living rooms (improvement, accounting for 30%). Building height limit: 80 meters (corresponding to 20 floors, each with a 4-meter height). Setback requirements: The main building must be ≥5 meters from the land boundary (north-south direction) and ≥3 meters (east-west direction).

[0034] Unit A (80 m2), standard floor plan: 12 m wide x 50 m deep (including balcony), balcony area 8 m2, including 2 m2 overlap with adjacent units (deduct 50% for 1 m2). Actual occupied area = 12 x 50 - 1 = 599 m2 / floor (excluding overlap).

[0035] Unit B (120 m2), standard floor plan: width 14 meters x depth 50 meters (including public corridor), corridor area 15 m2 (all deducted). Actual occupied area = 14 x 50 - 15 = 685 m2 / floor (excluding corridor area).

[0036] The project's volume ratio indicator data is processed to generate interval values ​​for the number of buildings. Land area: 50,000 m2 (300 meters long from north to south, 166.67 meters wide from east to west, rectangular plot); Volume ratio: 2.5 (total construction area capped at 125,000 m2); Target apartment types: 80 m2 two-bedroom, one-living room (basic needs, accounting for 70%), 120 m2 three-bedroom, two-living room (improvement, accounting for 30%). G1 module standard unit parameters: 80 m2 unit, 12 meters wide, 10 meters deep, standard floor area 120 m2 (including common area); 120 m2 unit, 14 meters wide, 10 meters deep, standard floor area 140 m2 (including common area).

[0037] The unit combination on a single floor is calculated as follows: 80㎡ units × 2 + 120㎡ unit × 1 = 2 units × 120㎡ + 1 unit × 140㎡ = 380㎡ / floor. Arranged in a north-south orientation, the 80㎡ units are on either side and the 120㎡ unit is in the center. The total width is 12 × 2 + 14 = 38 meters, and the depth is 10 meters, which is compatible with the 166.67-meter plot width (4-5 buildings can be arranged horizontally). The building area of ​​a single building (calculated based on 20 floors) is 380㎡ / floor × 20 floors = 7,600㎡ / building. 20 floors is a common residential height in the area, avoiding the complexity of super-high-rise approvals and meeting the 80-meter height limit (4-meter floor height × 20 floors = 80 meters).

[0038] The building number range is calculated as follows: Minimum building number (calculated based on saturated floor area ratio): Total building area must be ≥ 125,000 m2; Minimum building number = 125,000 m2 ÷ 7,600 m2 / building ≈ 16.45 buildings → rounded up to 17 buildings; Sunlight spacing must be ≥ 78 meters (as in the previous example). A single north-south building is 38 meters long and 78 meters apart, resulting in a single group of buildings occupying 38 + 78 = 116 meters. A 300-meter north-south plot can accommodate: 300 ÷ 116 ≈ 2.58 groups → 2 groups (4 buildings), leaving 300 - 2 × 116 = 68 meters, less than 116 meters, making it impossible to arrange a complete group. A purely north-south layout requires a minimum of 17 buildings (divided into 5 groups of 3-4 buildings each, with some spacing compressed to 60 meters, triggering a yellow alert).

[0039] The maximum number of buildings (calculated based on saturated land area) is: 38 meters (width) x 10 meters (depth) = 380 square meters. The theoretical maximum number of buildings = 50,000 square meters / 380 square meters = 131.58 buildings. The mandatory spacing requirement for sunny areas is 78 meters. Each building in the north-south direction must occupy 38 + 78 = 116 meters. The maximum layout is 300 / 116 = 2 rows, with 166.67 / 38 = 4.38 buildings per row, resulting in 4 buildings per row, for a total of 8 buildings. With a 5-meter setback from the property line on both the north and south sides, the actual usable length is 300 - 10 = 290 meters. This allows for 290 / 116 = 2.5 rows, resulting in 2 rows of 4 buildings per row, for a total of 8 buildings. Due to the constraints of sunny areas and setbacks, the actual maximum number of buildings is 8.

[0040] Call the standard unit data in the G1 module of the spatial module library. When assembling units into buildings, combine and splice each unit, automatically deduct the area of ​​the overlapping parts, record the standard floor outline information and the process and result data of the area deduction, and generate the basic unit assembly data. Building 1# is assembled from two units A (80㎡) and one unit B (120㎡). The standard floor plan is as follows: Unit A outline: 12m×50m, balcony area 8㎡ (overlapping area 2㎡, deduct 50% or 1㎡). Unit B outline: 14m×50m, public corridor area 15㎡ (all deductions).

[0041] The assembly process is as follows: horizontal splicing, unit A + unit B + unit A, total width = 12 + 14 + 12 = 38m, length 50m. Overlap area treatment: overlap the splicing seams between units by 1m 2 , according to the rules, deduct 50%, that is, 0.5㎡.

[0042] Total area of ​​a standard floor = (12 × 50 × 2 + 14 × 50) - (1 + 15 + 0.5) = (1200 + 700) - 16.5 = 1883.5 m2. Utilization rate = (1883.5 - 200 m2 of common area) ÷ 1883.5 = 89.4%. Unit assembly data is based on a standard floor profile of 38 m × 50 m, with 16.5 m2 deducted from the area, resulting in a utilization rate of 89.4%.

[0043] In another embodiment, standard unit data is obtained from the G1 module of the space module library. In the XX residential project in Pudong, Shanghai, the main apartment types are 80㎡ two bedrooms and one living room (just in case) and 120㎡ three bedrooms and two living rooms (improvement). The corresponding G1 module standard units are as follows: Unit A (80㎡), outline dimensions: width 12 meters × depth 50 meters (including balcony), balcony area 8㎡, overlapping part with adjacent units 2㎡ (deduct 50%, that is, 1㎡). The area occupied by the standard floor: 12×50-1=599㎡ (excluding the overlapping area). Unit B (120㎡), outline dimensions: width 14 meters × depth 50 meters (including public corridor), corridor area 15㎡ (full deduction). The area occupied by the standard floor: 14×50-15=685㎡ (excluding the corridor area).

[0044] The standard unit data was processed to generate the outline data for the standard floor. A single building is constructed using a horizontal layout of "Unit A x 2 + Unit B x 1," with a total width of 12 x 2 + 14 = 38 meters and a depth of 50 meters. The total area of ​​a standard floor is 599 x 2 + 685 = 1,883 square meters (excluding overlap and corridor areas). The standard floor outline is 38 meters x 50 meters, marking the unit boundaries and deduction locations (e.g., 1 square meter is deducted for balcony overlaps and 15 square meters is deducted for corridors).

[0045] The product positioning and design brief parameters in the project initialization information are processed to calculate the number and ratio of unit types in a single building, and generate building-level unit type indicators. Project positioning: The proportion of just-needed units is ≥ 70%, and the design brief requires the number of units in a single building to be ≤ 30. Number of floors: 20 (4-meter floor height, meeting the 80-meter height limit). Number of units in a single building: Unit A × 2: 20 floors × 2 units = 40 units (80-square-meter units). Unit B × 1: 20 floors × 1 unit = 20 units (120-square-meter units). Unit type ratio: 80-square-meter proportion = 40 ÷ (40 + 20) = 66.7% (close to 70%, requires adjustment).

[0046] Adjustment plan: Add one Unit A. The unit layout for a single building is Unit A x 3 + Unit B x 1. Total households = 60 + 20 = 80. The proportion of 80 square meters = 60 ÷ 80 = 75% (meeting the ≥ 70% requirement). Unit layout indicators for a single building: 60 units of 80 square meters and 20 units of 120 square meters, for a ratio of 75%:25%.

[0047] Obtain unit type indicators for all buildings and combine them with site initialization data, total number of households, total population, and the total area ratio of each unit type to generate basic indicators for the overall atlas. Land area: 50,000 m2 (rectangular plot, 300 meters north-south and 166.67 meters east-west). Floor area ratio: 2.5 → Total building area limit = 50,000 × 2.5 = 125,000 m2. Setback requirements: The main building must be ≥ 5 meters (north-south) and ≥ 3 meters (east-west) from the property line. The kindergarten must occupy an independent area of ​​≥ 2,500 m2. Height limit: 80 meters (corresponding to 20 floors, 4 meters high). G1 module standard unit parameters, specifically, Unit A (80 m2): Width 12 meters × Depth 50 meters, Balcony overlap area 2 m2 (deduct 50% to obtain 1 m2) → Actual occupied area = 12 × 50 - 1 = 599 m2 / floor. Unit B (120 m2): width 14 meters × depth 50 meters, public corridor area 15 m2 (fully deducted) → actual occupied area = 14 × 50 - 15 = 685 m2 / floor.

[0048] The construction and area calculation of a single building model are as follows: initial plan: unit A×2+unit B×1; standard floor area = 599×2+685=1883㎡ / floor; area of ​​a 20-story building = 1883×20=37660㎡; apartment ratio: 80㎡×40 households (2 units×20 floors), 120㎡×20 households (1 unit×20 floors) → 80㎡ accounts for 66.7% (less than 70%, needs to be adjusted).

[0049] The optimized plan is as follows: Unit A x 3 + Unit B x 1, with a standard floor area of ​​599 x 3 + 685 = 2,482 m2 per floor. The area of ​​a single 20-story building is 2,482 x 20 = 49,640 m2. Unit ratio: 80 m2 x 60 units (3 units x 20 floors), 120 m2 x 20 units (1 unit x 20 floors) → 80 m2 accounts for 75% of the total (meeting the ≥ 70% requirement). The outline and compliance of a single building: horizontal width = 12 x 3 + 14 = 50 meters, depth 50 meters, and usable site width after setback = 166.67 - 2 x 3 = 160.67 meters → 3 buildings can be arranged horizontally (50 x 3 = 150 meters < 160.67 meters).

[0050] The total number of buildings is calculated as follows, based on the saturated floor area ratio: Total building area must be ≤ 125,000 m2; single building area is 49,640 m2 → Maximum number of buildings = 125,000 ÷ 49,640 ≈ 2.52 → 3 buildings (rounded up, actual occupied floor area = 3 × 49,640 = 148,920 m2 > 125,000 m2, and any excess requires adjustment). The revised plan is as follows: Reduce one building, retain two → Floor area = 2 × 49,640 = 99,280 m2, Floor area ratio = 99,280 ÷ 50,000 = 1.985 < 2.5 (compliant).

[0051] The household and population indicators are as follows: single-building households = 60 households (80 m2) + 20 households (120 m2) = 80 households; total number of households = 2 buildings × 80 households = 160 households; total population = 160 households × 3.5 people / household = 560 people (calculated based on an average of 3.5 people per household).

[0052] The proportion of apartment area, total area of ​​80㎡ = 60 households × 2 buildings × 80㎡ = 9600㎡; total area of ​​120㎡ = 20 households × 2 buildings × 120㎡ = 4800㎡; area proportion = 9600:4800 = 2:1 (household types for basic needs account for 2 / 3, which is in line with the "basic needs-dominated" positioning).

[0053] The business zoning plan is as follows: Residential Area: Two high-rise buildings, covering an area of ​​2 × 50 × 50 = 5,000 square meters (including a 78-meter spacing, total north-south length = 50 + 78 = 128 meters < 300 meters). Commercial Area: On the east side of the plot, a two-story commercial building, covering an area of ​​1,000 square meters, with a construction area of ​​2,000 square meters (proportion = 2,000 ÷ 99,280 ≈ 2.0% < 10%). Kindergarten: Located in the northwest corner of the plot, covering an area of ​​2,500 square meters, with a construction area of ​​3,000 square meters (separately located to accommodate nine classes).

[0054] Compliance Verification: Floor Area Ratio: 1.985 < 2.5, compliant. Sunlight Spacing: 78 meters between buildings (60 meters in height × 1.3 coefficient), compliant. Setback Distance: 5 meters from the property line for residential buildings, 3 meters from the road for commercial buildings, compliant. Greenery Ratio: Greenery Area = 50,000 m2 - 5,000 m2 (residential) - 1,000 m2 (commercial) - 2,500 m2 (kindergarten), = 41,500 m2. Greenery Ratio = 41,500 ÷ 50,000 m2 = 83% (≥ 35%), compliant.

[0055] The initial three-building plan exceeded the floor area ratio (FAR). This was addressed by reducing the number of buildings and adjusting the apartment mix (increasing the proportion of Unit A) to ensure compliance. The conflict between sunlight spacing and the number of buildings: while reducing the number of buildings lowers the FAR, it avoids the potential for substandard sunlight due to reduced spacing (for example, the original three buildings needed to be spaced 50 meters apart, triggering a red alert). Rapidly generating metrics comparisons for multiple plans (e.g., two vs. three buildings) aids designers in decision-making. Business zones (blue for residential, yellow for commercial), spacing lines (78 meters), and setbacks are marked on the master plan to improve communication efficiency.

[0056] Based on the business format ratio rules in the multi-city rule board, the business format areas are divided in combination with the project positioning. Multi-city rule board (Shanghai): the commercial area accounts for ≤10%, and the supporting facilities (kindergarten) ≥3000㎡. The project is mainly positioned as residential, with community commerce and a 9-class kindergarten. Residential area: in the middle and north side of the plot, there are 3 high-rise buildings (arranged in a north-south direction, with a spacing of 78 meters). Commercial area: on the east side of the plot, a 2-story commercial building is planned, covering an area of ​​1000㎡ and a construction area of ​​2000㎡ (accounting for 2000÷125000=1.6%<10%). Kindergarten area: in the northwest corner of the plot, it covers an independent area of ​​2500㎡ and a construction area of ​​3000㎡ (meeting the requirements of 9 classes).

[0057] The business area is processed to generate business distribution indicators. Residential floor area: 49,640 m2 × 3 = 148,920 m2 (exceeding the floor area ratio limit and requiring adjustment). The adjustment plan is as follows: reduce one residential building and retain two. Residential area = 49,640 m2 × 2 = 99,280 m2. Floor area ratio = 99,280 ÷ 50,000 = 1.985 (compliant). Commercial to residential area ratio: 2,000:99,280 ≈ 2:100, meeting the commercial ratio requirement. The output is the business distribution indicator: 99,280 m2 (79.4%) residential, 2,000 m2 (1.6%) commercial, 3,000 m2 (2.4%) supporting facilities, with the remaining space being green space and roads.

[0058] Process the business distribution indicators to generate the overall map-level business indicators. Floor area ratio = 1.985 < 2.5, green area ratio = (50,000-3 residential base area-commercial / kindergarten area) ÷ 50,000 ≈ 38% ≥ 35% (compliant). Unit ratio: 80㎡ accounts for 75%, 120㎡ accounts for 25%, meeting the just-needed positioning. Setback compliance: residential areas are 5 meters from the red line, commercial areas are 3 meters from the road, and kindergartens are 50 meters from the road (all in compliance with Shanghai regulations). The final indicators are:

[0059]

[0060] An example of business logic series connection is as follows: data linkage: G1 module unit data → building assembly → general plan indicator calculation → business type zoning, with automatic association rules throughout the process (such as sunlight spacing, volume ratio, and business type ratio). Conflict handling: The initial plan has residential area exceeding the volume ratio, which is resolved by reducing the number of buildings and adjusting the apartment ratio, while ensuring that the sunlight spacing is compliant (78 meters). Visual output: Business type color: blue for residential areas, yellow for commercial areas, red for kindergartens, and automatic generation of spacing annotations (such as a 78-meter spacing line between buildings). Through the above steps, the system realizes the automatic generation and verification of indicators from unit modules to general plans, significantly improving the efficiency and compliance of map arrangement.

[0061] S103, processing the static spacing data, sunshine stick shadow map data, building quantity interval value, unit assembly basic data, building-level apartment type indicators and master plan-level business indicators to generate compliance verification results.

[0062] In one embodiment, the static spacing data, sunshine stick shadow map data, building number interval value and unit assembly basic data are processed to extract the sunshine spacing value, fire protection spacing value, setback distance and building height limit in the static spacing data, the shadow range period in the sunshine stick shadow map data, the minimum / maximum number of buildings in the building number interval value, the standard floor outline and overlapping area deduction value in the unit assembly basic data, the apartment area, ratio and utilization rate in the building-level apartment indicators, and the business area ratio and layout rationality information in the general map-level business indicators. The static spacing data are as follows: the actual measured value of sunshine spacing: 30 meters (standard value 78 meters, from the G1 module rule: high-rise spacing coefficient 1.3×60 meters height). The actual measured value of fire protection spacing: 30 meters (standard ≥13 meters, compliant). Setback distance: 8 meters on the south side and 6 meters on the north side (both ≥5 meters / 3 meters, compliant). Building height limit: 60 meters (≤80 meters, compliant). The data for the sunshine stick shadow chart is as follows: shadow coverage periods: 8:00-10:00 and 14:00-16:00, with a cumulative sunshine shortage period of 1 hour (standard ≥ 2 hours, triggering a yellow warning). The range of building numbers is as follows: the theoretical minimum number of buildings is 17 (full volume ratio), and the actual number of buildings that can be arranged is 8 (limited by sunshine spacing).

[0063] The basic data for unit assembly are as follows: standard floor outline: 38m×50m (unit A×2+unit B×1). Overlap area deduction: 1.5㎡ (balcony overlap 1㎡ + corridor deduction 15㎡). Utilization rate: 89.4% (standard ≥80%, compliant). Building-level apartment indicators are as follows: apartment area: 80㎡ (accounting for 66.7%), 120㎡ (accounting for 33.3%) → just-in-time demand accounts for less than 70%, with a deviation of -3.3%. Utilization rate: 89.4% (compliant). The business indicators at the general map level are as follows: commercial area ratio: 14.4% (standard ≤10%, exceeding the limit by 4.4%). Layout: Commercial is located on the east side, and the kindergarten occupies an independent area (compliant).

[0064] The extracted values ​​are compared with the spacing rules, sunlight standards, floor area ratio restrictions, area deduction rules, household allocation indicators, and business format matching rules in the multi-city rule dashboard, and the numerical deviation rate of each data item is calculated. The actual measured value of sunlight spacing is 30 meters, the standard value is 78 meters, and the deviation rate is calculated as follows: (30-78) / 78≈-61.5%, which is a red warning; the actual measured value of the proportion of housing needs is 66.7%, the standard value is ≥70%, and the deviation rate is calculated as follows: (66.7-70) / 70≈-4.7%, which is a yellow warning; the actual measured value of the proportion of commercial area is 14.4%, the standard value is ≤10%, and the deviation rate is calculated as follows: (14.4-10) / 10=+44%, which is a red warning; the actual measured value of fire protection spacing is 30 meters, the standard value is ≥13 meters, the deviation rate is calculated as compliant, and the result is green; the actual measured value of setback distance (south side) is 8 meters, the standard value is ≥5 meters, the deviation rate is calculated as compliant, and the result is green; the actual measured value of sunshine duration is 1.5 hours, the standard value is ≥2 hours, and the deviation rate is calculated as (1.5-2) / 2=-25%, which is a yellow warning.

[0065] The numerical deviation rate of each data item is processed to generate a compliance status indicator, and the corresponding rule clauses for the abnormal data are marked. The abnormal item in the static spacing report is: Sunlight spacing deviation -61.5%. The marking rule is: "High-rise residential spacing coefficient ≥ 1.3" in Article XX of the "Shanghai Urban Planning Management Technical Regulations." Compliance items: Fire separation distance, setback distance, and height limit are all compliant. The abnormal item in the sunlight shadow report is: Insufficient sunlight duration. The marking rule is: "Urban Residential Area Planning and Design Standard GB50180-2018" Article 4.0.9.

[0066] The building quantity report included a discrepancy between theory and practice: theoretically, 17 buildings were required (volume area ratio), but only 8 could be accommodated (due to limited sunlight spacing), prompting the user to "need to balance volume area ratio and sunlight requirements." The unit assembly report included compliance items: overlapping area deductions and utilization rates were both in compliance with G1 module rules. An anomaly in the apartment type indicator report included: 66.7% of the apartment types were for basic needs, marking the design brief requirement of "basic needs ≥ 70%." An anomaly in the business format indicator report included: 14.4% of the commercial area was for business, marking the Shanghai rule of "commercial ≤ 10%."

[0067] Compliance status and deviation details for each data item are summarized to generate compliance verification results, including static spacing compliance reports, sunlight and shadow compliance reports, building number rationality reports, unit assembly compliance reports, apartment type indicator compliance reports, and business type indicator compliance reports. The comprehensive report includes the following: High-risk items: Sunlight spacing (-61.5%), commercial area ratio (+44%) → Red alert, requiring immediate adjustment. Medium-risk items: Sunlight duration (-25%), apartment type ratio (-4.7%) → Yellow alert, suggesting optimization. Compliance items: Fire separation, setback distance, occupancy rate, building layout → Green mark. Visual output is a master map annotation: Red lines mark areas with insufficient sunlight and areas with excessive commercial space; yellow shading marks buildings with insufficient apartment type ratios. Data dashboard: Real-time display of deviation rates for each indicator and rule matching details, such as "Sunlight spacing does not meet standards, recommending an increase to 78 meters or adjusting the building layout."

[0068] Insufficient sunlight spacing limits the number of buildings. If strictly adhered to a 78-meter spacing, only three buildings can be arranged (the north-south area covers 38 + 78 × 2 = 194 meters, which is less than 300 meters). The floor area ratio = 3 × 49,640 = 148,920 square meters / 50,000 = 2.98, which is greater than 2.5, exceeding the floor area ratio. The commercial area exceeds the limit because the initial plan mistakenly included supporting areas as commercial. The actual commercial area should be adjusted to 12,500 square meters × 10% = 12,500 square meters, and the current 18,000 square meters needs to be reduced by 5,500 square meters.

[0069] The optimization plan is as follows: Sunlight adjustment: Adopt a staggered layout, reducing spacing to 60 meters (deviation -23%, yellow alert), allowing for four buildings. Floor area ratio = 4 × 49,640 = 198,560 m2 / 50,000 m2 = 3.97 > 2.5 → infeasible. Business adjustment: Reduce commercial area to 12,500 m2, accounting for 10%, meeting regulatory requirements. Unit type adjustment: Increase the number of Unit A units to four per building. The proportion of basic needs = 80 units / building × 4 buildings ÷ (80 + 20 units / building × 4 buildings) = 80%, meeting requirements.

[0070] The final compliant plan: 3 buildings (4 units A + 1 unit B / building), 78 meters apart, with a floor area ratio of 3 × (599 × 4 + 685) × 20 ÷ 50,000 = 2.49 ≈ 2.5, which is compliant. Sunlight hours: Through a staggered floor design, the first floor of Building 2 receives 1.8 hours of sunlight (still insufficient and requiring solar compensation). Commercial space: 12,500 square meters, representing 10% of the total area, which is compliant.

[0071] Through the standardized process of "data extraction → rule comparison → deviation identification → report generation", the system has achieved multi-dimensional compliance coverage: covering more than 10 rule verifications such as sunlight, spacing, business types, and apartment types to avoid manual omissions. Risk classification management: red / yellow / green three-color identifications intuitively display the severity of the problem, and high-risk items are handled first. Data-driven optimization: Provide quantitative deviation values ​​and rule basis to assist designers in quickly locating problems (such as the root cause of commercial area exceeding the limit is supporting miscalculation). Efficiency improvement: Compared with traditional manual verification (20 hours), the system automatically generates reports in only 0.5 hours, an efficiency improvement of 97.5%. Ensure that the master plan strikes a balance between compliance and design goals, and provide a foundation for subsequent automated layout and AI optimization.

[0072] S104: Process the compliance verification results and generate potential problem solution information.

[0073] In one embodiment, the static spacing numerical deviation rate, sunshine shadow period deviation rate, building number interval deviation rate, unit assembly deduction deviation rate, building-level apartment index deviation value, and general plan-level business index deviation are extracted from the compliance verification results. Key deviation indicators are extracted from the compliance verification results, as follows: static spacing numerical deviation rate: the sunshine spacing is measured to be 30 meters, the standard is 78 meters, and the deviation rate is -61.5% (significantly substandard); the fire protection distance is 30 meters (≥13 meters, compliant). Sunlight shadow period deviation rate: the sunshine period is 1 hour, the standard is 2 hours, and the deviation rate is -25% (yellow warning). Building number interval deviation rate: the theoretical minimum is 17 buildings (the volume ratio is saturated), and in reality only 8 buildings can be arranged (subject to sunshine restrictions), with a deviation rate of -52.9% (needs to balance indicators). Unit assembly deduction deviation rate: the overlapping area is deducted by 1.5㎡, which complies with the G1 module rules (compliant). Deviation of building-level unit indicators: 66.7% of units meet basic needs, 70% target, -3.3% deviation (yellow alert). Deviation of master plan-level business indicators: 14.4% of commercial area, ≤10% target, +44% deviation (red alert).

[0074] Each deviation rate is compared with the preset threshold to generate a deviation limit mark. The preset threshold rules are as follows: Red warning: Deviation rate > ±10% or touching the mandatory rules (such as sunshine spacing, commercial ratio). Yellow warning: 5% < Deviation rate ≤ ±10% (such as sunshine duration, apartment ratio). Green compliance: Deviation rate ≤ ±5% (such as fire spacing, setback distance). The marking results are sunshine spacing (-61.5%), commercial area (+44%) → red mark. Sunshine duration (-25%), apartment ratio (-3.3%) → yellow mark. Fire spacing, setback distance, unit assembly → green mark.

[0075] Process the deviation exceeding limit marks, classify them by project positioning, city rules, and module call status, and mark the rule clauses and data flow nodes corresponding to the exceptions. Classified by project positioning: the commercial proportion in residential projects exceeds the limit, marked as "commercial supporting facilities exceed the standard, and the area needs to be compressed." Classified by city rules: sunlight spacing does not meet the standard → Article XX of the "Shanghai Urban Planning Management Technical Regulations" (high-rise spacing coefficient ≥ 1.3). The commercial proportion exceeds the limit → "Shanghai Commercial Business Planning Guidelines" (commercial proportion ≤ 10%). Classified by module call status: sunlight calculation is based on the "sun trajectory model" of the G1 module, and there is no call exception; the commercial area calculation mistakenly includes supporting facilities → data input node exception (manual mislabeling of supporting facilities attributes).

[0076] After categorization, deviation violations, rule clauses, and data flow anomaly records are summarized and categorized to generate potential problem solution information, including a solution compliance score, anomaly type distribution, and module call success rate. Specifically, the overall score is 65 points (out of 100, with 20 points deducted for each red item and 5 points deducted for each yellow item). Anomaly type distribution includes rule-related anomalies: sunlight (35%), commercial (35%), apartment type (15%), and sunlight duration (15%). Data-related anomalies include errors in commercial area statistics (100%). The module call success rate includes a G1 module rule matching success rate of 90% (sunlight and spacing rules are called normally, but commercial rules are not matched due to data input errors). Data flow records include anomaly nodes: the manual input stage (commercial area miscalculation) and the module calculation stage (automatic verification of sunlight spacing). Exceeding the commercial area limit and insufficient sunlight spacing are both high-risk items and require priority. Commercial area can be quickly optimized by adjusting business zoning (e.g., reducing the number of floors in commercial buildings), while sunlight spacing requires adjustments to building layout or height, which is more complex.

[0077] The commercial area was compressed from 18,000 m2 to 12,500 m2, accounting for 10%, and the trigger rule match was successful. The number of buildings was reduced from 10 to 8, and the spacing was adjusted to 78 meters, sacrificing the volume ratio to 1.985 (compliant). At the same time, the staggered design increased the sunshine duration to 1.8 hours (close to the standard). The visual output includes general map markings: red areas mark commercial areas that exceed the limit and buildings with insufficient sunshine; yellow areas mark units with insufficient apartment ratios. Data report: List the basis for each abnormal rule, comparison of indicators before and after adjustment, and attach module call logs (such as errors in the commercial area calculation steps).

[0078] Through a process of "data extraction - threshold determination - classification and tagging - summary reporting," the system transforms complex compliance issues into structured exception information, helping designers quickly identify core issues (such as excessive sunlight, floor area ratio, and commercial proportion), and providing regulatory basis and optimization directions. This highly automated process improves efficiency by over 70% compared to traditional manual investigations. Multi-dimensional classification ensures comprehensive coverage of issues and avoids missing key compliance items.

[0079] S105, processing the potential problem solution information based on the feature dimension to generate intelligent general map auxiliary map arrangement abnormality information.

[0080] In one embodiment, the potential problem solution information is processed according to the characteristic dimensions, and the solution compliance score, anomaly type distribution, module call success rate, rule matching abnormal clauses, and data flow node abnormal records are extracted. Key dimension data are extracted from the potential problem solution information: Solution compliance score: The comprehensive score is 65 points (out of 100 points), of which the sunlight spacing (-20 points), commercial proportion (-20 points), sunlight duration (-5 points), and apartment type ratio (-5 points) are the main deduction points. Anomaly type distribution: rule-based anomalies account for 85% (sunlight 35%, commercial 35%, apartment type 15%), and data-based anomalies account for 15% (commercial area statistical errors). Module call success rate: The overall success rate of the G1 module is 90%, of which the sunlight calculation module is successful and the business rule matching fails (due to manual mislabeling of the supporting area).

[0081] Rule matching exception clauses: Sunlight spacing: Article XX of the "Shanghai Urban Planning Management Technical Regulations" (high-rise spacing coefficient ≥ 1.3). Commercial ratio: "Shanghai Commercial Business Planning Guidelines" (commercial area ratio ≤ 10%). Data flow nodes: Manual input stage (commercial area miscalculation), module verification stage (sunlight spacing automatically triggers an alert).

[0082] The correlations between feature dimensions were processed to generate an analysis of the proportion of anomaly types, the distribution of reasons for module call failures, and the distribution of cities where rules did not match. There was a compliance issue with sunlight spacing (accounting for 35%). Symptom: The measured distance between Buildings 1 and 2 in the project was 30 meters, far below the Shanghai regulatory requirement of 78 meters (60 meters building height x 1.3 coefficient), with a deviation rate of -61.5%, triggering a red alert. Impact: This directly limited the number of buildings: only three could be arranged according to the standard spacing, resulting in a floor area ratio of 1.985, below the target of 2.5, necessitating a compromise in floor area ratio or violating spacing regulations. Insufficient sunlight duration: The south-facing windows on the first floor of Building 2 received 1.5 hours of sunlight, failing the standard of ≥2 hours on the Great Cold Day, impacting residents' right to daylight. Source of conflict: The site's north-south length was limited to 300 meters. If a strict adherence to the 78-meter spacing were to be adhered to, the number of buildings would be reduced from the planned 10 to 3, making it difficult to balance floor area ratio and living quality. Traditional manual map arrangement relies on empirical estimation without real-time association rule verification, which leads to disruptive adjustments to the plan later.

[0083] Commercial space planning issues (accounting for 35%): Symptoms: Commercial space accounts for 14.4% (measured at 18,000 square meters), exceeding the Shanghai limit of 10% (standard value of 12,500 square meters), with a deviation rate of +44%, triggering a red alert. Impact: Violation of local planning guidelines may lead to approval rejection; an unbalanced business mix squeezes residential and supporting space, impacting project economics. Root cause: Designers mistakenly included supporting areas such as kindergartens and community service centers in the commercial area, resulting in statistical discrepancies; a lack of real-time business classification verification tools makes manual calculations prone to errors.

[0084] Statistical errors in commercial area (accounting for 15%) include error types and impacts. Specifically, the error is an operational error: the designer mistakenly selected "commercial attributes" to supporting facilities in the "supporting construction definition" link, resulting in an inflated commercial area of ​​5,500 square meters (the actual commercial area should be 12,500 square meters, but it was mistakenly calculated as 18,000 square meters). System feedback: The G1 module automatically recognized that the area exceeded the limit during verification, but the data source was not located, and the input fields needed to be manually checked line by line. The data flow log shows: "Commercial area = supporting construction area + commercial building area". The formula logic is correct, but the supporting construction area attribute label is incorrect.

[0085] Process optimization needs, including pain point exposure: the data input interface lacks clear business classification guidelines (such as commercial / supporting / residential are not marked in separate columns), leading to manual errors; improvement direction: add a drop-down menu to force classification (such as "commercial / public services / municipal facilities"), and configure a real-time data verification pop-up window (such as automatic prompt when the commercial proportion exceeds 10%).

[0086] Module call failure reasons: Data input errors accounted for 100% of the total, rule matching mechanism and failure link. Module logic: The G1 module invoked the "Shanghai commercial share ≤ 10%" rule from the multi-city rule dashboard. Combined with the input total building area (125,000 square meters), it calculated the commercial area limit to be 12,500 square meters. Failure points included the manual input stage: the designer mistakenly marked 3,000 square meters of supporting area as commercial, resulting in the input value of 18,000 square meters exceeding 12,500 square meters; the verification stage: the module triggered a red alert, but did not indicate a data source error, only displaying "commercial area exceeds limit."

[0087] Human-machine collaboration optimization points, system improvements: Add a "Business Area Composition Details" pop-up window on the data input interface, display the commercial / supporting / residential proportions in real time, and mark the over-limit items with different colors (such as red marking the commercial part that exceeds the upper limit); Operation training: For high-frequency misoperations (such as mislabeling of supporting attributes), a prompt guide is embedded in the system. For example, when clicking the "Commercial Area" field, a rule description pops up: "Commercial proportion ≤ 10%, supporting facilities are not included in the commercial area."

[0088] Rule matching integrity and rule base compatibility verification. Coverage: Project-related requirements for sunlight spacing, commercial ratio, and setbacks all align with local regulations, including the "Shanghai Urban Planning Management Technical Regulations" and the "Shanghai Commercial Business Planning Guidelines," with no missing rules or outdated versions. Verification value: Ensures system verification results have legal validity, avoiding compliance risks caused by missing rules.

[0089] As a potential optimization direction, for local special rules such as the "sunshine duration compensation mechanism" (such as allowing some housing types to supplement sunshine duration through solar facilities), parameter configuration entries can be added to the G1 module to support designers' flexible adjustments.

[0090] Integrating user behavior data to identify inefficient operational links corresponding to abnormal solutions. Analysis of user behavior data (such as operation logs) revealed that the designer mistakenly classified the kindergarten's supporting area as commercial during the "business format definition" phase, resulting in an inflated commercial area. Furthermore, multiple attempts to manually adjust the daylight spacing to 60 meters (triggering a yellow alert) failed to trigger automatic optimization suggestions, indicating room for improvement in the system's spacing adjustment guidance. Inefficiencies included manual data entry accuracy (accounting for 30% of operation time) and rule conflict resolution efficiency (accounting for 40% of the design cycle).

[0091] The feature analysis results are visualized to generate a plan-level anomaly report, visual markers, and data flow logs. The plan-level anomaly report has the following cover: project name, score 65, and generation date. The main text contains high-risk items: sunlight spacing (deviation -61.5%) and commercial ratio (deviation +44%), along with rules and adjustment suggestions (such as "increase building spacing to 78 meters" and "re-divide commercial and supporting areas"). Medium-risk items: sunlight duration (deviation -25%) and apartment ratio (deviation -3.3%). It is recommended to adopt a staggered-level design or adjust the unit mix. Data flow records include screenshots of commercial area miscalculation nodes and module call log details. Visual markers are a general map superimposed with red shading to mark areas with insufficient sunlight (1st-3rd floors of Building 2) and red-filled areas with excessive commercial space; yellow dotted lines mark buildings with insufficient apartment ratios (Building 1). A dynamic dashboard displays the deviation rate of each indicator and the rule matching status (such as "failed" for sunlight rules and "pending revision" for commercial rules) in real time. The data flow log includes a timeline record of the entire process: "Manually enter the commercial area → G1 module verification → Trigger red alert → Designer adjustment → Re-verification and approval." Key node details: Before and after the commercial area was revised from 18,000 square meters to 12,500 square meters, with the module's automatic calculation process.

[0092] Problem identification: Through feature analysis, it was determined that the core contradiction is the conflict between sunlight and commercial indicators. The root cause lies in manual data input errors and deviations in the understanding of rules. Optimization path: Re-divide the business areas, remove the supporting areas that were mistakenly marked as commercial, and adjust the commercial area to 12,500 square meters (accounting for 10%). Reduce the number of buildings to 3, maintain the spacing at 78 meters, and increase the volume ratio to 2.49 by increasing the number of unit floors (22 floors), which is close to the target value. The apartment combination is adjusted to unit A×4+unit B×1, and the proportion of rigid demand is increased to 80%. Efficiency improvement: Through the visual report automatically generated by the system, designers only need 2 hours to complete the scheme adjustment (the traditional process takes 10 hours), which improves efficiency by 80%.

[0093] Through the process of "feature extraction - association analysis - behavior location - visual output," the system transforms abstract compliance issues into actionable optimization guidelines. This not only enables structured presentation of exception information but also infers design process pain points through user behavior data, providing a basis for tool iteration. This process demonstrates the core value of intelligent master plan assistance tools in data-driven design, automated verification, and visual communication.

[0094] In one embodiment, Figure 2 As shown, the present application also provides an intelligent master map auxiliary arrangement device based on module calling and automatic verification, comprising:

[0095] Acquisition module 201, used to obtain basic data for intelligent general map auxiliary arrangement;

[0096] The processing module 202 is used to call and pre-process the basic data, call the spatial module library G1 module with one click, realize the data flow from G1 to G3, and generate static spacing data, sunshine stick shadow map data, building number interval value, unit assembly basic data, building-level apartment type indicators and general map-level business indicators based on the multi-city rule dashboard; process the static spacing data, sunshine stick shadow map data, building number interval value, unit assembly basic data, building-level apartment type indicators and general map-level business indicators to generate compliance verification results; process the compliance verification results to generate potential problem solution information; process the potential problem solution information based on the feature dimension to generate intelligent general map auxiliary layout exception information.

[0097] Each embodiment in this application is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the evaluation of the intelligent master map auxiliary arrangement method based on module call and automatic verification, electronic device, electronic device, and readable storage medium embodiment, since it is basically similar to the above-mentioned intelligent master map auxiliary arrangement method embodiment based on module call and automatic verification, the description is relatively simple, and the relevant parts can be referred to the partial description of the above-mentioned intelligent master map auxiliary arrangement method embodiment based on module call and automatic verification.

Claims

1. An intelligent master plan auxiliary arrangement method based on module calling and automatic verification, characterized in that: include: Obtain basic data for intelligent master plan auxiliary layout, including project initialization information, spatial module library G1 module data, multi-city rule dashboard data, manually arranged master plan and indicator data; Perform module call and preprocessing on basic data, call the G1 module of the spatial module library with one click, realize the data flow from G1 to G3, and generate static spacing data, sunshine stick shadow map data, building quantity interval value, unit assembly basic data, building-level apartment indicators and master plan-level business indicators based on multi-city rule dashboards; Process static spacing data, sunshine stick shadow map data, building quantity interval values, unit assembly basic data, building-level unit type indicators and master plan-level business indicators to generate compliance verification results; Process compliance verification results and generate potential problem solution information; Potential problem solution information is processed based on feature dimensions to generate intelligent master map auxiliary layout exception information, where the intelligent master map auxiliary layout exception information includes solution-level exception reports, visual markings, and data flow logs.

2. The method according to claim 1, wherein Perform module call and preprocessing on basic data, call the G1 module of the spatial module library with one click, realize the data flow from G1 to G3, and generate static spacing data, sunshine stick shadow map data, building quantity interval value, unit assembly basic data, building-level apartment indicators and master plan-level business indicators based on multi-city rule dashboards, including: Based on the sunlight calculation rules and fire separation distance standard data built into the G1 module of the spatial module library, as well as the city-specific spacing parameters extracted from the multi-city rule dashboard, combined with site topography data, building coordinates and orientation data, a geometric algorithm is used to calculate the minimum sunlight separation distance and fire separation distance values ​​between buildings, thereby generating static spacing data; Generate building orientation based on the site's geographic coordinate data and building orientation data; The G1 module uses the building model of the sun's altitude and azimuth angles over time, as well as the local sunshine standard data in the multi-city rule board. By simulating the angle and position of sunlight on the building model at different time periods, the graphics rendering algorithm is used to generate the sunshine shadow range data of each building at different time periods, and generate sunshine stick shadow map data. Obtain land area data from the project initialization information, and obtain unit area data and building standard floor outline data from the G1 module of the spatial module library; Process the project's volume ratio index data to generate interval values ​​for the number of buildings; Call the standard unit data in the G1 module of the spatial module library. In the process of assembling units into buildings, combine and splice the units, and automatically deduct the area of ​​the overlapping parts. Record the standard layer outline information and the process and result data of the area deduction to generate the basic data for unit assembly.

3. The method according to claim 2, wherein The basic data is called and pre-processed by modules. The G1 module of the spatial module library is called with one click to realize the data flow from G1 to G3. Based on the multi-city rule dashboard, static spacing data, sunshine stick shadow map data, building quantity interval value, unit assembly basic data, building-level apartment indicators and master plan-level business indicators are generated. It also includes: Get standard cell data from the G1 module of the spatial module library; Process the standard unit data to generate vulnerability standard layer contour data; Process the product positioning and design brief parameters in the project initialization information, calculate the number and ratio of apartment types in a single building, and generate building-level apartment type indicators; Obtain the apartment type indicators of all buildings, combine them with the site initialization data, the total number of households, the total population and the total area ratio of each apartment type, and generate the basic indicators of the overall atlas; Based on the business format ratio rules in the multi-city rule board, the business format areas are divided in combination with the project positioning; Process the business areas and generate business distribution indicators; The business type distribution indicators are processed to generate the overall map-level business type indicators.

4. The method according to claim 3, wherein Static spacing data, sunshine stick shadow map data, building quantity interval values, unit assembly basic data, building-level unit type indicators and master plan-level business indicators are processed to generate compliance verification results, including: Static spacing data, sunshine shadow map data, building number interval values, and unit assembly basic data are processed to extract sunshine spacing values, fire protection spacing values, setback distances, and building height limits from the static spacing data, shadow range periods from the sunshine shadow map data, the minimum / maximum number of buildings from the building number interval values, standard floor outlines and overlapping area deduction values ​​from the unit assembly basic data, unit type area, ratio, and utilization rate from the building-level unit type indicators, and business type area ratio and reasonable layout information from the master map-level business type indicators. Compare the extracted values ​​with the spacing rules, sunlight standards, floor area ratio restrictions, area deduction rules, household allocation indicators, and business format allocation rules in the multi-city rule dashboard, and calculate the value deviation rate of each data item; Process the numerical deviation rate of each data item, generate a compliance status identifier, and mark the rule clauses corresponding to the abnormal data; Summarize the compliance status and deviation details of each data item, and generate compliance verification results including static spacing compliance report, sunlight shadow compliance report, building quantity rationality report, unit assembly compliance report, apartment type index compliance report, and business format index compliance report.

5. The method according to claim 1, wherein Process compliance verification results to generate potential problem solution information, including: Extract the static spacing value deviation rate, sunlight shadow period deviation rate, building number interval deviation rate, unit assembly deduction deviation rate, building-level apartment index deviation value, and master plan-level business index deviation from the compliance verification results; Compare each deviation rate with a preset threshold and generate a deviation exceeding limit mark; Process the deviation exceeding limit mark, classify it by project location, city rules, and module call status, and mark the rule clauses and data flow nodes corresponding to the exception; Summarize and classify the deviation limit exceeding marks, rule clauses and data flow exception records, and generate potential problem solution information including solution compliance score, exception type distribution and module call success rate.

6. The method according to claim 5, wherein Based on the characteristic dimensions, potential problem solution information is processed to generate intelligent master plan auxiliary layout exception information. The intelligent master plan auxiliary layout exception information includes solution-level exception reports, visual markings, and data flow logs, including: Process potential problem solution information based on feature dimensions to extract solution compliance scores, exception type distribution, module call success rate, rule matching exception clauses, and data flow node exception records; Process the correlation between feature dimensions to generate analysis of the proportion of abnormal types, distribution of reasons for module call failure, and distribution of cities where rules do not match; Combine user behavior collection data to locate inefficient operation links corresponding to abnormal solutions; Visualize the feature analysis results to generate solution-level exception reports, visual markers, and data flow logs.

7. An intelligent general map auxiliary arrangement device based on module calling and automatic verification, characterized in that: The device comprises: The acquisition module is used to obtain the basic data for intelligent general map auxiliary layout; The processing module is used to call and preprocess the basic data, call the G1 module of the spatial module library with one click, realize the data flow from G1 to G3, and generate static spacing data, sunshine stick shadow map data, building number interval values, unit assembly basic data, building-level apartment type indicators and general map-level business indicators based on the multi-city rule dashboard; process the static spacing data, sunshine stick shadow map data, building number interval values, unit assembly basic data, building-level apartment type indicators and general map-level business indicators to generate compliance verification results; process the compliance verification results to generate potential problem solution information; process the potential problem solution information based on the feature dimension to generate intelligent general map auxiliary layout exception information.

8. An electronic device, characterized in that: include: a first processor; and a memory for storing executable instructions of the first processor; The first processor is configured to execute the intelligent master map auxiliary arrangement method based on module calling and automatic verification as described in any one of claims 1 to 6 by executing the executable instructions.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by the second processor, the intelligent master plan auxiliary arrangement method based on module calling and automatic verification as described in any one of claims 1 to 6 is implemented.

Images