Many thanks Nick!
I will use it as you suggested. Basically, I had a solution for it, although it is NOT what I want. My solution was to use only LI code for line strings as follows:
So, I abandoned the polygon (area feature) code PP and used only line feature code (LI), where the CLO control code means CLOSE to the first point of the sequence.
It works as expected both in TA and TBC. The "problem" is that I have to perform some additional actions in TBC after Feature Code Processing, since by using my approach I get
only line strings (no polygons) and I need an area (polygon) as a result. It practically means I have to use the ANZ command Convert To Polygon,
after selecting the lines between points 74-75-76-77-78-79-80 -81-82-82-74 and this is also not desired (the additional work).
Basically, my idea is to omit TBC for this purpose and perform it in real time in TA only, then export the coded line work within TA to SHP with correct topology (no overlapping line/s)
and send the results by email from the field to the customer. Customer requires NO overlapping line/s.
So again - thank you!
Martin
------------------------------
Martin Kalafut
------------------------------
Original Message:
Sent: 11-26-2023 19:35
From: Nick Mein
Subject: Different behaviour of coded line work in TBC v2023.10 and Trimble Access v2023.10 which use the SAME FXL library
Hi Martin,
Absolutely agree that TA and TBC should produce the same result, and that TBC is correct. In your case, perhaps a solution would be to code it like this, which is a little simpler, and gives the same (correct) result in TA and TBC
Best regards,
Nick.
------------------------------
Nick Mein
Original Message:
Sent: 11-25-2023 14:33
From: Martin Kalafut
Subject: Different behaviour of coded line work in TBC v2023.10 and Trimble Access v2023.10 which use the SAME FXL library
Hello,
I encountered a strange thing (problem) regarding the use of the same FXL library used in TBC and TA.
I created a FXL library using latest Feature Definition Manager (FDM):
Here is an overview of the used codes in the FXL library and displayed in the pictures below:
PP - polygon feature definition (code) for an area feature (parking area as a whole)
LI - line feature definition (code) for a line dividing parking lots each other
ST - line control code for the start of a line joining sequence
IGN - ignores any joining operation
JTSP - joins to specified point name
In TA the coded line work looks as follows (it is NOT as expected, it is wrong):
I downloaded the TA JXL file into a TBC project, where I processed the feature codes and the results looks like this (this is as expected, this is correct)
When I remove the control code IGN from the points 81, 82 and 83 in TA 2023.10, then TA joins
the point 81 with 78, 82 with 77 and 83 with 76 (creates the required lines between them),
however, when I process it in TBC (with removed IGN control code on points 81, 82 and 83), although even TBC also creates
the required lines, there (in TBC) is also created a whole undesirable line between the points 78-81-82-83-76 (see picture below):
The line overlaps polygon line in the section between points 81-82-83 and is absolutely undesirable,
although the logic in TBC is OK when it creates this undesirable line taking the coding without IGN line control code into account.
Where is the problem in Trimble Access 2023.10 logic that performs NO required joining between the points pairs 81-78, 82-77 and 83-76
when using IGN control code as described above?
Martin Kalafut
------------------------------
Martin Kalafut
------------------------------