Vector List in TBC
Quote from Deleted user on August 6, 2024, 11:17 amNo.
There are quite a few hidden metadata available to be turned on in the Vector List Report, but Feature Code is not one of them.
Apparently, Feature Codes are affiliated with Points, and do not describe the mathematics/geodesy that goes into resolving/measuring a vector.
No.
There are quite a few hidden metadata available to be turned on in the Vector List Report, but Feature Code is not one of them.
Apparently, Feature Codes are affiliated with Points, and do not describe the mathematics/geodesy that goes into resolving/measuring a vector.
Quote from OleManRiver on August 7, 2024, 12:50 pmI have not ran TBC in almost a year. I had a client that required data that was in the vector list and other information that was not. I ended up creating a custom export to csv along with doing the vector list itself and another report and combined what I needed and eliminated what I did not need. It took a little time but I was able to get it done. I had all the steps written down and was going to try and build a custom report that could do it without have to export and copy and paste from several different things.
I would not think that a feature code would be in a vector list as a vector is made up from two different points that might have two different feature codes.
There is a lot of options in the custom export options to pick and choose and order and arrange which I used often for custom stake out data required by different entities.
I have not ran TBC in almost a year. I had a client that required data that was in the vector list and other information that was not. I ended up creating a custom export to csv along with doing the vector list itself and another report and combined what I needed and eliminated what I did not need. It took a little time but I was able to get it done. I had all the steps written down and was going to try and build a custom report that could do it without have to export and copy and paste from several different things.
I would not think that a feature code would be in a vector list as a vector is made up from two different points that might have two different feature codes.
There is a lot of options in the custom export options to pick and choose and order and arrange which I used often for custom stake out data required by different entities.
Quote from jimcox on August 7, 2024, 2:30 pm> I would not think that a feature code would be in a vector list as a vector is made up from two different points that might have two different feature codes.
Indeed they might - But the convention is to use the code(s) on the start point of the line
> I would not think that a feature code would be in a vector list as a vector is made up from two different points that might have two different feature codes.
Indeed they might - But the convention is to use the code(s) on the start point of the line
Quote from WallyP on September 2, 2024, 7:28 amWhat i want, is just a description of the point at either end of the vector line, so like 3000 (Base) to 7561 (Brass Bolt). This way the Vector List would be more descriptive. As it is now you'd have to try to remember what feature each point number was.
What i want, is just a description of the point at either end of the vector line, so like 3000 (Base) to 7561 (Brass Bolt). This way the Vector List would be more descriptive. As it is now you'd have to try to remember what feature each point number was.
Quote from OleManRiver on September 4, 2024, 7:02 pmSo I did a rough jab at this today. It was on a site I had a few hundred RTK vectors to. I selected them and copied from the vector list to excel. I then exported the points at rover end and made a custom export that had the point name and feature code. I copied that into a sheet in excel. I then just went to the third sheet in excel and matched the point name from the custom export using the point name at RTK rover to match to the vector sheets point name and gave it a rule that said if this equals this then place this here. So took a few minutes tops. If I would have thought it through I would have sorted the vector list via the rover to point name and copied to excel then from that selection opened the point sheet report sorted the same and copied it right beside the same vector list. If this is something you do a lot not just a one time thing. Then once in excel write a macro that eliminates the unneeded columns like northing easting duplicate point id’s. Excel is very powerful. If I ever get a chance to learn how to write the Trimble macros inside of TBC then I could do this probably within that to make one report.
So I did a rough jab at this today. It was on a site I had a few hundred RTK vectors to. I selected them and copied from the vector list to excel. I then exported the points at rover end and made a custom export that had the point name and feature code. I copied that into a sheet in excel. I then just went to the third sheet in excel and matched the point name from the custom export using the point name at RTK rover to match to the vector sheets point name and gave it a rule that said if this equals this then place this here. So took a few minutes tops. If I would have thought it through I would have sorted the vector list via the rover to point name and copied to excel then from that selection opened the point sheet report sorted the same and copied it right beside the same vector list. If this is something you do a lot not just a one time thing. Then once in excel write a macro that eliminates the unneeded columns like northing easting duplicate point id’s. Excel is very powerful. If I ever get a chance to learn how to write the Trimble macros inside of TBC then I could do this probably within that to make one report.