thanks for taking time out to look at that.
the hunter was the start of my survey career. I was the young assistant for Travis on the other bridges going over the F3. and I assisted you once doing a level run for the control pillars under the push bridge you were working on. I also assisted Jason and Ryan from geometric.
Original Message:
Sent: 09-16-2024 20:16
From: Ronny Schneider
Subject: bug - no join control code processing
Hi Peter,
I had a quick look during lunchtime. I do see the same behavior in 2023.11 and 2024.00. So, it's nothing new.
I do see your point though and would say it is a bug. Even though no line is supposed to be created it should at least relayer the points. But it seems to completely ignore the points once it sees the "don't join code". If you use the "start line" or "end line" code for each point it does relayer them, but of course you'll get one-point polygons.
You'll have to send this to UPG and they need to push it to Trimble. But the chances are high that this is considered a feature and not a bug and they most likely suggest that you use a specific point code for the ones you don't want as lines.
------------------------------
Ronny Schneider
Original Message:
Sent: 09-16-2024 16:18
From: Ronny Schneider
Subject: bug - no join control code processing
Hunter Express Way feels like a lifetime ago. Had to find my CV, which obviously hasn't been updated since 2019, and see that this was 2011/12.
I'm getting old. I'm racking my brain to place you.
I'll have a look tonight and try to replicate this.
------------------------------
Ronny Schneider
Original Message:
Sent: 09-16-2024 15:46
From: Peter Batson
Subject: bug - no join control code processing
Hey mate,
it's been a while since the Hunter expressway.
I'm currently running version 2024.1.
------------------------------
Peter Batson
Original Message:
Sent: 09-16-2024 14:29
From: Ronny Schneider
Subject: bug - no join control code processing
Which version are you running?
There is a major feature code processing bug in 2024.00, with numeric codes and multi coding. I've heard rumors that it's been fixed in 2024.01, but it wasn't included in the release notes for that one.
------------------------------
Ronny Schneider
Original Message:
Sent: 09-16-2024 14:21
From: Peter Batson
Subject: bug - no join control code processing
I've notice that TBC will not process my survey points that have a polygon code and a no join control.
scenario:
I was doing an as-built survey of a road surface post milling. I first surveyed the perimeter of the areas using my WRMIL1 (polygon code + string number), then on the larger areas I surveyed some points in the middle using the same code different string number WRMIL2. in TBC I first processed the data unchanged, and everything did as it should all points and polygons went to their set layers. this created unwanted polygons on the middle points. to remove this, I added the no join control code and reprocessed and found TBC didn't process these points and left them in the points layer. I know I could just delete the unwanted polygons, but the FXL are meant to minimize as much manual process as possible.
I'm also trying to keep my FXL to a manageable size. so, having a point, line and polygon code for the same surface feature could be avoided by using control codes.
I've also noticed the "included in surface" point property when creating codes also effects the line/polygon. I think this should be separate choice if you want the line/point to be included or both. in my opinion if a point to processed into a line or polygon it should not be included (the line should). but if it's not a part of a line or polygon it should.
open to suggestions
regards
------------------------------
Peter Batson
------------------------------