An additional question for this post.
I have also used UDPs on the drawing side. I have been able to import UDP data after I have brought in points from data base. I create a text file withe the point number and then the udps. On the import It will ask me to ovewirte or merge, because of the duplicate point number. I am able to merge them and it add the UDP data.
I have recently been trying to do this in the survey data base and have not been able to get it to work in the same mannor. I import an ascii file and it goes thur the motions, but does not add any data to the UDPs i created in the survey database. It does not prompt me to merge or overwrite data. I am assuming that it wont let me add additonal UDP data to the existing points in the database. I am assuming I will have to add it when I bring in my data originally. Which I won't be able to, unless I change my procedures, because I bring in most of my data a .fbk files.
So I am wondering if I am missing something? Is it possible for me to bring in a seperate ascii file with just point number and UDPs to my exisiting points in the survey database, like I can do in a drawing?
The LandXML import procedures into a Survey Database were always slightly more robust. Your only hope to after-the-fact add UDP information to previously brought in survey data that orignally came in as a filedbook is to use XML.
I'm not saying it will work, nor do I know how you would go about creating the XML file with the similar point numbers, with your desired UDP.
You might be asking too much of the Survey Database. It has a hard enough time processing traditional ground survey data in the polar format.
One thing you might want to consider, albeit less than ideal... is to run two survey databases; one for actual ground data which was populated by field work, this one you would use to reduce and balance the work, and to serve as the central repository of "Survey" data. The second SurveyDatabase could be populated by coordinate data only, fed through the XML method. This secondary database could be considered the "GIS" database - the one that holds the extended data. In my office the "extended data" could contain Utility Pole information, Sewer Inverts, Drainage inverts, house numbers, tree species data, etc. If you really paid attention, you could populate drawings from each database for the specified information needed.