求助：在XAML/C#中开发Win10原生交互式建筑PDF地图应用

Hey there! Let's tackle this room mapping challenge for your Win10 native app—since that old Silverlight answer is way out of date, here are some modern, practical approaches that fit right into UWP/WinUI 3 development:

PDFs are static by nature, so you’ll need to render them into a canvas where you can overlay interactive elements. For Win10 native apps, these are your best bets:

• Use the built-in Windows.Data.Pdf namespace to parse PDF pages and render them as BitmapImage or WriteableBitmap—this gives you a solid background layer without relying on third-party tools.
• For more granular control (like rendering specific layers or vector elements), go with SkiaSharp (Google’s cross-platform graphics library with full UWP/WinUI support). It’s lightweight, fast, and makes it easy to mix PDF rendering with custom interactive shapes.

This is the heart of your problem—here’s how to handle both manual and semi-automated room mapping:

Manual Annotation (Great for Small-to-Medium Maps) #

If your PDF doesn’t have extractable vector room outlines, manual labeling is straightforward and reliable:

• Overlay an InkCanvas on top of your rendered PDF background. Let users draw closed polygons around each room (you can restrict ink to polygon mode for precision).
• Assign a unique ID to each drawn polygon, then link it to room details (store this mapping in a lightweight local database like SQLite, or a JSON file if you prefer simplicity).
• To handle clicks: Listen for pointer events on the canvas, convert the click coordinate to the canvas’s local space, then use Geometry.Contains(Point) to check which polygon the click falls inside. Trigger your room info display once you find a match.

Semi-Automated Extraction (For Vector-Based PDFs) #

If your PDF was exported from a CAD tool (like AutoCAD) as a vector file, you can skip manual drawing by extracting room outlines:

• Parse the PDF’s vector content using libraries like PdfSharpCore or the advanced path extraction tools in SkiaSharp. Filter out non-room elements (like walls, corridors) to isolate closed paths that represent rooms.
• Clean up the extracted paths: Merge small fragments, remove duplicate lines, and ensure each path is a closed polygon.
• Auto-generate IDs for each cleaned polygon, link to room data, and use the same click-detection logic as the manual workflow.

• Add zoom/pan: Wrap your canvas in a ScrollViewer and handle ManipulationDelta events to support gesture-based zooming and panning—critical for large building maps.
• Speed up click detection: If you have dozens/hundreds of rooms, don’t check every polygon on every click. Implement a quadtree spatial index to split your canvas into regions; only check polygons in the region where the click occurred. This drastically reduces the number of checks needed.
• Use WinUI 3 controls: If you’re targeting newer Win10 versions or Win11, WinUI 3’s Canvas and InkCanvas have better performance and touch support than older UWP controls.

• PDF parsing: Windows.Data.Pdf (native, free) or PdfSharpCore (open-source, cross-.NET)
• Graphics rendering: SkiaSharp (fast, flexible, great for custom shapes)
• Local storage: SQLite-net-pcl (lightweight ORM for storing room mappings and details)

内容的提问来源于stack exchange，提问作者ntenBroek