Should I ever decide to resurrect this project, I am thinking that I would scale things back somewhat, at least initially. Aside from the challenge of reading the binary files, I was also running into a lot of difficulty rendering track splines correctly, and the code for showing and hiding objects in the map was getting unwieldy as well. So I think it might be better to start with a much simpler tool, and then see how it can evolve over time.
By scaled back, I mean that this version would not display a map. Instead it would simply show a tree grouping items by category and KUID, and a list showing instances of the KUID selected in the tree. The list will still show the map location of each item instance, so if you turn on the cursor position display in Surveyor, you should be able to navigate to any item quite easily.
The initial iteration would provide the ability to print a report of items used, but since it would not include a map display, it would not print track. I realize that is a highly desirable feature, but again, I am thinking about how we can make ‘something’ available sooner rather than later.
So I guess my question is, would such a scaled back tool still be useful in terms of asset analysis? I think it would be; and again, once a basis is in place, hopefully the tool can be expanded over time.
Looking forward to your feedback.
Regards,
Mike