I find myself translating and rotating control and boundary points into other files a lot. Sucks, but it happens when you always start a project on 1000, 1000 coordinate system for all the decades past.
Generally this company has always started control at point number 1 for a project and found monuments at 50. Calculated points can be anywhere between 100 & 999, then topo or mapping starts at 1000.
At times, boundary and control get translated rotated and I always have to renumber points. Usually just adding 100 to them.
But then years down the road I do it again, and again, and then eventually two things happen:
1. I lose track of where a point came from (What job # and the date we tied it).
2. I end up running out of 101, 201, 301, 401... ranges.
I've considered adding in a date and field crew number to every point but that gets messy in my mind. So I think using the job no. will work. Like in Job number 1584 point 1 when it gets translated rotated make it 1_1584 or something like that.
Is anyone using a point numbering system like this? What better ways are there to fix this little problem?
1-200 Control, 200-500 Calculations, 500-800 RWM, 800-1000 Property monuments.
1000+ topography
This is DOT numbering system that all the engineers locally followed, so we got used to it. Modify it as it fits with your situation. Clearly 1-200 for control isn't necessary for most jobs in the GPS era and 500-800 for right of way is a DOT thing. I do fill up the 200-500 for calc points often, but those are usually erasable points, keep them in the range and delete as needed. If you keep the point numbers organized it can be very helpful.
1-99 Control
100-399 Boundary
400-499 Search Calcs
500-999 Corner calcs for staking
1000-1999 As-staked record shots
2000-2999 Building/Structure Staking Calcs
3000-3999 Sanitary Staking Calcs
4000-4999 Storm Staking Calcs
5000-5999 Water staking Calcs
6000-8999 Curbs/Roads staking Calcs
9000-9999 Misc. staking calcs
10000+ Topographic Mapping
Also, resected instrument positions are numbered by date. Such a point established today would be 231025. If there were going to be more than one such position today it would be 231025a, 231025b, and so on. C3d can't handle such alpha points, but I don't want them there anyway. StarNet can handle it OK.
I use alpha numeric for control and boundary corners. Comps or calcs have a alpha prefix as well. As staked of a calc gets a new prefix added or suffix. All control starts with a two letter so AB the then the county abbreviation so CO. So AB zn N or S for north south then a number. The number never ever gets re used. This allows me to come back and do an adjoining property and know that corners number and ck as well as any control. The prefix and or suffix is easily removed in a text editor on the instance i have to give it to cad folks. Thats one example. Another for a specific client. Alpha two letters tract number and a new number all in one so AB2121_100 control. Property corner PC2121_500. So point range at end to easily identify control from property corners like y’all mentioned. Now i do this as it allows me to easily manage data not just for a specific job but to have a database that is built overtime. We have not put this into full production yet and are tweaking it prepping for the new datum. Its not anything new really i sorta played off of the PID scheme on ngs data sheets and some other govt work i did globally for control. Just have to keep a running list with multiple crews working i. Same county on different jobs etc. it would be much easier if it could be full alpha all the time. You could incorporate company initals part chief job number. Have a designated for static vs rtk levels total station etc. lots of ways to do it with alpha and numeric. Only if autodesk would not freak out. If i had my own company it would e a no brainer as i would have a gis database that would be easily accessible to export control corners withen a certain distance area of any project. But i am a little crazy so I enjoy the easiness of organization and knowing exactly what is what especially differentiating control corners comps etc quickly It adds a little extra hump to managing by layers only etc.
Thank you for all of those... great food for thought.
Now, when you have two projects that get rotated to the same basis of bearing, and want all the points together in one file.... Now you have two point number 1's (or whatever). How would you change point numbering systems so that you could keep track? That is my main goal. (Or am I the only one with this problem?)
I can count on one hand the number of times I have rotated points in the last 10 years, and those were all "oh ^&$#!" moments.
I rotate blocks of linework all the time, but once field data are in a drawing file, those points stay on whatever datum we post-processed in, and the linework is drawn to that.
If I were bringing in old data and absolutely HAD to take the points with it, I'd bump them all by 100000 or something so I know which points are old (not observed with current survey) and could note that on the new survey. But then again, I'm not certifying that a monument is there if I haven't verified it for the current survey, so I likely wouldn't ever be bringing in points from the old file in the first place....just the linework.
If I have to translate/rotate one survey onto another I'll attach the survey to be moved as an xref.
I don't rotate points. With the exception of bringing them into a different job using their lat, long, height value from one projection to another. If that can be considered a "rotation".
Points with the same number need to get edited. It's a bookkeeping process, we usually deal with it in TBC prior to the points getting into CAD.
Begin your point numbers with the Julian date. You will then only have duplicates if they were created exactly 1 year apart.
