• State Not Answered
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 4625 views
  • Users 0 members are here

Problems with detailed cell object when creating automated iDPR

Mike001
Offline

Hi

If I have many cell objects that looks like this (very close up zoom level) and I have approximatly 700 dgn files convering a big extent. The cell is made up by many line string objects and one circle object and one point.

When i convert the dgn files using automated iDPR in BGWP administraton program the cell ending up looking like this:

If I increase precision to maximum 100 and convert a smaller extent area (less dgn files, 25 files) I can get the cell to look like this:

Which is better than the above but still not like it look in the original. And preferable I would like to convert many files at a time not have to set up 100 of diffrent automated iDPR jobs

 

So what would be the best way to make the cell look good via wms created by BGWP ? Its not necessary to view all the different lines within the circle, but its a must to see that its a triangle within a circle.

 

Parents
  • 0 Offline
    Hello Mike,

    Is that a pattern in the cell? I think there might be a way to manipulate the patterning during iDPR conversion. If you attach an example I can check that.

    Regards
    Carlos



  • 0 Offline in reply to CMartins
    Thanks ( again :) ) for the reply.
    Would you like an example of the cell (if so in what format?) or an example of the ipdr conversion parameters?
  • 0 Offline in reply to Mike001
    This was enough, I can easily replicate the issue.

    If the cell had a pattern (I was hoping for that) we could either disable patterning in the seed or use a pentable to resymbolize it, unfortunately it doesn't, it only contains an Arc, Line Strings and a point, no patterns. This means as far as I know that there is no easy solution...

    You can consider replacing the cells by a new and “simpler” cell, one without those ‘inner’ line strings. In MicroStation the Replace Cells Tool in the Cells toolbox enables you to replace all the cells in a DGN. For multiple DGN a batch can be used.

    Another alternative but more complicated would be to create a ODBC/Spatial layer, if you have the XY coordinates of each point-cell you can then symbolize the point-cell with any symbol.

    Regards,
    Carlos



  • 0 Offline in reply to CMartins
    I will check if those alterantive suggestion is an option for me in this case.

    But do you know why when having low resolution and converting many dgn files (big extent) at the same makes the cell, in the wms, become a huge grey circle ?

    I would understand if it just became a circle in the same size/form as the outer circle in the cell, but thats not the case.
    It is perhaps not possible to see in the images I posted in the first post, but the filled grey circle then gets at least 10 times big as the "cell circle". Any idea on this?

    Br
    Mike
  • 0 Offline in reply to Mike001
    Resolution affects how many units of resolution will be mapped to physical units such as meters, if the resolution is low and the extents are very large those lines in the cell that are very closed to each other may result in the display that looks more like a filled circle. The cell element contains a lot of details (many string lines) and with such conversion large extents it isn't really suitable, the size being 10 times bigger could be a consequence of that but it seems very extreme.

    Regards
    Carlos



  • 0 Offline in reply to Mike001

    I had another look at the cell and I strongly suspect 'the huge grey circle' is caused by the point element in the cell. I changed the color for better viewing


    I copied and scaled the cell just beside one of the cells, I run the conversion and the result is this one (the red line is just there for location purposes, don't mind with that). On the left the circle is covering in fact the entire cell,  on the right the copied/scaled cell is partly visible, and you can see the same circle with the same size, it's the point... 

    I believe the solution could be to get rid of this point, ideally achieve this during iDPR conversion but the fact the point is part of the cell doesn't make things easy.



  • 0 Offline in reply to CMartins
    Hi Carlos

    I have thought about that also and the problem is, as you say, how to remove it from the cell and be sure that it never comes back. For it doesn't (at least for me) look like you can filter it away in a easy way using the filtering options in BGWP (perhaps in using key ins, but those I havn't figured out how to use).

    However, if I get the tDPR to work with a good result (either by changing resolution or font) I guess the problem above isn't so big since each get processed with its own extent. Therefore the point still gets big, but not "10 times bigger" as when I ran multiple .dgn files.

    Br
    Mike
Reply
  • 0 Offline in reply to CMartins
    Hi Carlos

    I have thought about that also and the problem is, as you say, how to remove it from the cell and be sure that it never comes back. For it doesn't (at least for me) look like you can filter it away in a easy way using the filtering options in BGWP (perhaps in using key ins, but those I havn't figured out how to use).

    However, if I get the tDPR to work with a good result (either by changing resolution or font) I guess the problem above isn't so big since each get processed with its own extent. Therefore the point still gets big, but not "10 times bigger" as when I ran multiple .dgn files.

    Br
    Mike
Children
No Data
Communities
Support and Services
Training and Learning
Social Media