Trimble Business Center

 View Only
Expand all | Collapse all

FXL Process Re-Layer

  • 1.  FXL Process Re-Layer

    Posted 04-06-2020 08:56

    I have experienced a problem when I relayer my lines and point after doing a "Process Feature Codes".  I relayer all my lines and point even thou my FXL has specific layers onces processed.  We do a bit of topos and i just want a layer to bring in my topo as why i have a specific layer they go in.  After I relayer, I modify the line processed and it will re-re-layer my lines and points back to the original layer and reprocess the points/lines.  What would cause the work to be placed back in the original layers?



  • 2.  Re: FXL Process Re-Layer

    Posted 04-16-2020 14:33

    I recently had this happen again.  Request to have this bug fixed. 



  • 3.  Re: FXL Process Re-Layer

    Posted 04-19-2020 08:14

    I had this reported to me in November last year and it is a known issue on the Geospatial side. There is a "backdoor fix" for this and I will post it today for you that stops this from happening, but I agree it does need a better fix long term.

     

    I will come back later today on this as I have to recall the fix

     

    Alan



  • 4.  Re: FXL Process Re-Layer

    Posted 04-20-2020 10:03

    This question has come up a few times recently, so I recorded the video below to show the issue and how to solve it in TBC.

     

    The problem posed is that you import a data file from e.g. Trimble Access and you then process feature Codes to create the linework drawing and to appropriately tag all the data as Include In Surface or not. Having processed the feature Codes, you then select all of the data and make a surface model. At this point you realize that the surface is not forming quite right in certain areas because of feature codes that were incorrect in the field. So you go into our point data properties and change the feature codes on the appropriate points and then you re run Process Feature Codes to update the drawing.

     

    The problem is as follows. On doing the above, the second time you process feature codes, all linework is deleted and recreated regardless of whether or not the feature coded points of those lines were changed or not. The side effect of this is that those new lines are not a part of the surface model that you created from the original linework after the first Feature Code Process. It can be a little tricky to spot that this happened, because the triangulation changes may be subtle (the points are still in the surface, it is the breaklines that got removed. If you turn off the Feature Lines and Turn On Breaklines in the Surface properties the change is more evident.

     

    To solve the problem, you can add the imported file (JXL or SPJ from Access or Siteworks) to the surface model and this will make sure that whenever you process Feature Codes for that "Data Block" that the linework that is generated from the Processing will be included in the Surface Model. The reason for this is that the Linework created from processing a Data Block is added to the Data Block automatically, so if the Data Block is included in the surface, then the Linework generated from processing the Data Block is also added to the surface automatically.

     

    The video below shows you the problem and how to address it in TBC v5.21

     

    Click Here to download the video

     

    Hope that this helps

     

    Alan



  • 5.  Re: FXL Process Re-Layer

    Posted 04-22-2020 03:41

    This actually happens not involving any modifications to the processed feature codes.  I will open the layere to view tie in elevations and location,  I will not do any changes after we process the codes.  The data controller we have has Survey Pro installed.  I will have to check at a later time if the JXL or SPJ are an option for Survey Pro.



  • 6.  Re: FXL Process Re-Layer

    Posted 04-22-2020 08:41

    I would have to get a Survey Pro file to look at as I dont get involved

    with that at all

     

    Alan

     

    On Wed, Apr 22, 2020 at 4:41 AM frank.guerrero@ebcc.com <trimble@jiveon.com>



  • 7.  Re: FXL Process Re-Layer

    Posted 05-26-2020 13:59

    will a .DC file work ??



  • 8.  RE: Re: FXL Process Re-Layer

    Posted 03-30-2021 10:44
    I still have problems with my processed points being moved back to their layers and at times adding duplicate lines from when they are processed.  I have the idea now to explode the lines and then remove the processed.  Maybe this will fix my issue.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 9.  RE: Re: FXL Process Re-Layer

    Posted 03-30-2021 13:17

    Just curious about what's going on.

    From your original description, when you say that you modify one of the lines (that was processed) - what kind of modification are you doing?

    And after you do that modification, does it suddenly re-layer and re-process the lines and points (without any interaction from you)?

    Or are there a few steps between the modification and the re-layer/process part?



    ------------------------------
    Quan Mueller
    Revenant Solutions - TML Development
    ------------------------------



  • 10.  RE: Re: FXL Process Re-Layer

    Posted 03-30-2021 16:37
    The created FXL has layer where each item goes in after being processed. The modifications or changes I make are to linestring that cross to another point when they should stop say at point "G" .  So I delete segments.  Another one is when, say I have edge asphalt and edge of curb gutter linestring that cross each and I need to move/nudge a point so the lines don't cross.   Not sure if anyone else does any modifying of their processed data, I do and it was a pain relayed into so many time.  We will see how the explode line macro works for me.  It will be some testing as there is the explode all segments or angles.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 11.  RE: Re: FXL Process Re-Layer

    Posted 03-31-2021 07:00
    from what you are describing i believe this is not a glitch. there is a setting in the feature codes proccessing settings that says "redraw all feature codes when computing project". in your case you should unselect this choice and then any modifications you make should be held when computing the project after feature codes have been drawn. 
    otherwise any line changes(segments errased) would have to been done with the coding. for example adding stop and start line control codes. because any time the drawing is computed(red dot) all feature lines/symbols are redrawn. this can be an advantage in our case where we need the codes to be perfect so that they will draw correctly when imported into civil3d as this is a requirement for one of our clients. 
    layer control is embeded into the fxl, so i am not certain how you could overcome this other than changing the fxl so that all your topo points are on the layer you want. ideally it would be setup correctly from the start. 
    hope this helps. ian

    ------------------------------
    ian bissonnette
    ------------------------------



  • 12.  RE: Re: FXL Process Re-Layer

    Posted 03-31-2021 07:13
    One other thing I forgot to mention is once I have all my data processed, I i relayer all those points and linestring to a new layer.  If I was to"redraw"  my data will be relayered.  I need to relayers and I have pre, during, and post topo/as-builts point that are processed.  To not overlap points and lines i have one layers setup for the process step and then I relayer after that.    I am not sure how others handle their "process feature code" process.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 13.  RE: Re: FXL Process Re-Layer

    Posted 03-31-2021 08:14
    one approach is to have different codes for the different stages of the project that would draw onto the correct layer. example TOP OG and TOP FG. top original ground and top finished grade. this can work for general earth works jobs but for civil work there are likely too many codes.
    i have not used it too much but i think you can reference another project from a master tbc project. so you could have one project for your original ground and one for during and one asbuilt. then in the master project you could see all these and do drafting or surface comparisons. similarly we export linework and point into cad and adjust as needed there. this way your layer and line tweaks should he preserved.
    hopefully this helps.




  • 14.  RE: Re: FXL Process Re-Layer

    Posted 03-31-2021 08:35
    the one approach aint gonna happen.  I still see the explode as y best option for now until we are able to have multiple FXL inside TBC.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 15.  RE: Re: FXL Process Re-Layer

    Posted 03-31-2021 10:24
    the advantage of having the codes on the correct layer is that it is all automatic and you would no longer have to do any of this work. but i understand not wanting to change systems already in place. 

    so if you turn off process feature codes on compute. and then when you bring in your next set of data, you only process the new data. then you should get what you are after. i think anyways. in theory you could load another fxl and run the next set of data with it.





  • 16.  RE: Re: FXL Process Re-Layer

    Posted 03-31-2021 11:01
    On compute, you choose which files to process. That would do nothing for me.
    replacing the inplace FXL will if I remember correctly remove your old FXL linework.  no workie there neither.

    ------------------------------
    Francisco Guerrero
    ------------------------------



  • 17.  RE: Re: FXL Process Re-Layer

    Posted 04-06-2021 12:54
    Attempted the explode linestrings on another project that I have already processed.  fail.  Something like 95% of the linestrings exploded and the other 5% did not.  That 5% was left as processed linestrings.  Which I will test them when they are still in their original layer not in the re-layered layer.

    ------------------------------
    Francisco Guerrero
    ------------------------------