This is a UX situation that occurs in many object-oriented or rich visual design programs where a visual objects onscreen have rich metadata. Examples:
- Computer Aided Design (CAD) for physical objects and systems
- Interior design (where materials and components may have a lot of metadata)
- Electrical circuit design
- Graphical programming languages (LabView, 4GL's, etc)
- Project management software
- Building Information Management (BIM)
In these apps, it's common to want to search object properties, but also to show the search results onscreen.
A typical pattern used is to:
Provide a list of search results somewhere because lists can organize results better when the metadata or the object(s) are not visible onscreen. Lists also have lots of other advantages for search results such as readability, scannability, UX navigability, etc.
Allow the user to navigate to 1 result or all results using the visual representation
Here's an illustrative example using a sidebar to accomplish the search and provide a list of results. A callout (dark orange background) allows particular results to also display related metadata:
There are many variations on this basic pattern, which can include:
- Showing all results visually, instead of selecting one at a time (i.e. just outline all search results in orange and show more infrmation on hover)
- Showing the search results and also a separate panel for the metadata/properties (rather than a callout)
- Allowing the user to toggle between list view and schematic view for search results
You will need to tailor this approach for your application and users' specific needs, but this pattern should give you a start.
If you want to do more research, I'd suggest getting trial copies of some of the CAD/Design programs above and seeing how search works.