Update sample.txt

sample.txt

@@ -1,24 +1,45 @@
-The client’s core challenge is that their current drawing process is heavily manual. Equipment attributes are manually typed across GAs, One-lines, Relaying Diagrams, and DC Schematics. They want to transition to a smart, connected workflow.
+import ezdxf
+from collections import Counter
 
-Based on the customer's priorities, they want to start with simple integrations first. Please review the requirements broken down into our proposed four-phase roadmap:
+def count_components_with_details(file_path):
+    try:
+        doc = ezdxf.readfile(file_path)
+        inventory = []
+        
+        for layout in doc.layouts:
+            for insert in layout.query('INSERT'):
+                name = insert.dxf.name
+                
+                # Filter out system/meta blocks
+                if name.startswith('*') or name == 'WD_M' or 'TB' in name.upper() or 'TTLB' in name.upper():
+                    continue
+                
+                # 1. GET THE PICK POINT (Insertion Point)
+                # Returns a Vector object (x, y, z)
+                ip = insert.dxf.insert
+                pick_point = f"({ip.x:.2f}, {ip.y:.2f})"
+                
+                # 2. Extract attributes
+                raw_attribs = {att.dxf.tag: att.dxf.text for att in insert.attribs if att.dxf.text.strip()}
+                attr_str = " | ".join([f"{k}: {v}" for k, v in raw_attribs.items()])
+                if not attr_str:
+                    attr_str = "(No Attributes)"
+                
+                # We store the pick point along with name and attributes
+                inventory.append((name, pick_point, attr_str))
 
-Phase 1: Foundational Component Linking
-•	Smart Interconnectivity: The fundamental "step one" is making 2D symbols smart. A component (e.g., Breaker 52-L1) on a General Arrangement (GA) drawing must be digitally linked to that exact same symbol on the One-line and Relaying diagrams.
-•	AutoCAD Source: The solution must seamlessly integrate with their base AutoCAD files, which serve as their primary source of truth.
+        print(f"=== DETAILED INVENTORY FOR: {file_path} ===")
+        print(f"TOTAL COMPONENTS: {len(inventory)}")
+        print("-" * 120)
+        print(f"{'Block Name':<20} | {'Pick Point (X,Y)':<18} | {'Attribute Details'}")
+        print("-" * 120)
+        
+        for name, p_point, attrs in inventory:
+            print(f"{name:<20} | {p_point:<18} | {attrs}")
 
-Phase 2: Attribute Propagation & Logic Checking
-•	Data Flow: If an engineer enters standard equipment parameters on the One-line (e.g., from a vendor print), that data must automatically propagate to the corresponding DC Schematics.
-•	Automated Flags: The system should perform basic cross-drawing checks (e.g., verifying that if relay 50-L1 is meant to trip breaker 52-L1, the connection is correctly reflected in the schematics) and flag discrepancies for human review.
-
-Phase 3: AI-Driven Generative Design & Compliance
-•	Generative AI: Utilizing AI trained on historical data and protection philosophies to infer and generate project-specific elements (like close/trip coils).
-•	Audit Trail: Crucial requirement. The system must generate a clear "decision tree" showing how the software arrived at its conclusions. Their legal team requires this to prove responsible charge for the signing engineer.
-
-Phase 4: Ancillary Data Extraction (Future Tools)
-•	Automated Cable Lists: Once the core integration is stable, the system should scan the schematics using OCR/Vision AI to extract cable loops, color codes, and connections, automatically populating this data into an Excel spreadsheet.
-
-Requested Sample Files As requested during our internal discussions, I have attached the sample files so you can visualize the required data flow. Please find the following attached:
-•	AutoCAD files
-•	PDF Files
-•	Equipment BOM (303.01)
+    except Exception as e:
+        print(f"Error: {e}")
 
+# Usage
+file_path = r"C:\Users\navinshrivatsan\Desktop\dxf_one_line_drawings\NRE-EC-101.0.dxf"
+count_components_with_details(file_path)