Vero/dragndrop_hld
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit - Stage 1 working version

Browse Source 
Saving current working state before proceeding to Stage 2.
Includes:
- Backend: Python-based QC validator with shapefile processing
- Frontend: Drag-and-drop file upload interface
- Sample files for testing
- Documentation and revision history

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Alexander Hall
2025-12-04 13:43:57 -07:00
commit 12407b74e4
147 changed files with 8524 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
revisions2/revisions2.txt
+12
View File
@@ -0,0 +1,12 @@
Backend:
-add this as next QC step after existing ones, before returning to front end:
1. Ensure all sites features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all sites.
2. Ensure all access_points features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all access_points.
3. Ensure all permits features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all permits features.
4. Ensure all splicing features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all splicing features.
5. Ensure all network_elements features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all network_elements features.
6. Ensure all poles features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all poles features.
7. Ensure all segments features are within the correct cabinet boundary. Make sure the 2-digit number in the cabinet_boundaries feature "Name" field matches the 2-digit number in the "Group 1" field for all access_points. EXCEPTION: If a segment crosses between cabinet_boundaries polygons, don't evaluate it.
8. Ensure NO features are outside of the entirety of the cabinet_boundaries polgyons layer
Like with previous QC efforts, return list of specific issues in the .txt file if it does not pass QC