Export to tab-file doesn't make sence

Geospatial Desktop Products

This is where you can find and contribute to discussions, ideas, and other information about Bentley Geospatial Desktop products.

Export to tab-file doesn't make sence

  • rated by 0 members
  • This post has 7 Replies |
  • 2 Followers
  • Brilliant - thank you very much :-)  Could you update me of the easiest way to delete the tags? I used to use key-in "fence freeze and fence thaw" - but I don't think this is enough?

     

    /Bo.

  • We have looked at your data and can confirm that exporting tags causes various problems at this time.  We intend to fix this in our next major release which is expected in Q4 of this year.  For now, the best thing to do is to delete the tags using the remove tags tool.  This means removing all the tag sets from the drawing.  Naturally you will have made a copy of the DGN beforehand!

    To have Bentley Map not recognize cells based on cell name, simply define the variable MS_GEOXFM_NO_CELLNAMEFEATURES =1

    This should enable feature recognition only on level names.

    I hope this helps

     Keith Raymond

    Bentley Canada

  • Oops - I just realized I usually have my regional settings set to the following: decimal delimeter: ","- changing this made the units right? - I guess this is a small bug - but it should be corrected.

     Please  try to do an export to a TAB-directory. When doing so you will find that the export crashes due to the existence of tags (element type 37). After one crash all units are devided with something like 100.000 after to crashes it starts dividing by 1.000.000 and so on? I think it would be better if the export just skipped the tag-information!

     Another thing I miss is to be able to tell the export to use the levelname rather than the cell-name when exporting these features. We have experieced that this is caused by Dynamic Feature Scoring - as mentioned before we often use session-based xfm-schemas, and here we would like to be able to use the level name....

     Looking forward to hearing your reply :-)

    /Bo.

  • ScreenShot106.jpg

    Hi again

     I am happy to hear that you are not experiencing problems - because then all I need to figure out is where I need to do something diferent. I have attached the file from yesterday withot the mapModel which will only cause problems. When I create a Mif/Mid file i get the attached output where the coordinates are divided with 1000. Please note that PowerMap doesn't give MapInfo the correct projection settings. I have attached an image with a screendump with the projection settings within Powermap.  In the export it says "nonEarth coordinates"?

    Please try to perfom an export to a tab-directory and select all layers - I am very curiuous if this works for you :-)

     Thank you very much for your help so far...

    /Bo.

     


  • In the skel level, I found about 40+/- point lines at coordinate 0,0 in the drawing. Seeing that the skel level was what looked like street lines, and these were way off from the rest of the data, I deleted these point elements. Once I did that I could export the tab file. After I exported it, I reattached the tab file back to the drawing as a reference file, and it overlayed the original data perfectly ( even took into account the view rotation you had). Is this what you are seeing ? I don't know if the points mean anything in you data set, or not.

     

    HTH

    Jerry

  • Hi Jerry

     Sorry - I wrote a little more yesterday, but the browser froze... Heres a little more explanation:

    When performing the export everything is moved to something that looks like 0,0. I would like to export all layers, but try exporting the layer "skel".

    After some further testing we have enden up using dxf-version 11 and then import this into MapInfo. However this isn't our prefered setup. As far as I can tell a lot of our problems has to do with our use of tag-element (element type 37) it seems to bring the export function "on its knees" when it meets a tag? However this isn't all we are facing - it seems our units are divided by 100.000 and another isue is the handling of XFM-features. We are using features in some of our production and here we have seen errors that has to do with our use of "session based XFM-schemas". PowerMap doesn't update this schemas when you open change files without closing PowerMap entirely.I have seen some similar errors when trying to perform this export: I have seen a lot of differnet version of what is shown in the export. I think this has to do with me exporting one tab-file and later opening the same file - however I haven't qute figured out yet what is happening but noticed, that for instance the layer "skel" in some cases shows the feature "length" and in other cases shows another description?

    I hope the above makes sence!

     Regards

     Bo.

  • Which feature or all of them ???

    Jerry

  • 001_1_ramme-001-2d-100296.dgn
    Hi When I try to export the attached designfile to MapInfo (I have tried all three versions: tab-file, tab-directory and MIF/MID) - I get a useless result. Powermap lists elements to length "0" and it looks like my coordinates are divided by approx. 100.000? The export makes absolutely no sence - please test the attached file thanks in advance Bo.
Page 1 of 1 (8 items)