MapInfo Pro

 View Only

  • 1.  Clean makes .MAP bigger

    Posted 11-22-2018 19:14
    I have observed some unusual behaviour with the Clean command.
    I am running MapInfo 64-bit version 16.0.3

    I have a table containing one record, a very large polygon, which is the result of buffering railway tracks.
    The original .MAP had a file size of 5,789 KB
    The original polygon had 728,840 nodes

    I ran the Clean command on the table (without the Overlap or Gap Area keywords)

    The new .MAP had a file size of 11,455 KB
    The new polygon had 713,647 nodes

    The change in number of nodes does not worry me. It is almost the same, and is easily explained by being a result of cleaning.
    But, why has the .MAP file doubled in size? The number of nodes has not doubled. Is there something different in the way the geometry has been stored?


    ------------------------------
    Nick Lawrence
    TMR
    ------------------------------


  • 2.  RE: Clean makes .MAP bigger

    Posted 11-22-2018 20:00
    Hi @Nick Lawrence - quick question: have you tried running a Pack table after the clean & did this change the size of <g class="gr_ gr_133 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" id="133" data-gr-id="133"><g class="gr_ gr_132 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" id="132" data-gr-id="132">the</g> .</g>MAP <g class="gr_ gr_140 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" id="140" data-gr-id="140">file  ?</g>

    ------------------------------
    Ashley Crane
    Regional Director, Software Support
    Pitney Bowes
    ------------------------------

    Original Message


  • 3.  RE: Clean makes .MAP bigger

    Posted 11-22-2018 20:51
    I ran Pack and it went back to the original size.

    ------------------------------
    Nick Lawrence
    Mr
    TMR-Policy and Planning
    Brisbane
    ------------------------------

    Original Message


  • 4.  RE: Clean makes .MAP bigger
    Best Answer

    Employee
    Posted 11-22-2018 23:04
    Thanks Ashley.
    And Nick, this behavior is by design and as expected. The doubling in size result is an extreme case given your file on has one large polygon. The clean operation does nothing to a polygon if no cleaning is required. In your case the one polygon needed cleaning and inside the file the old version of the polygon is flagged as deleted and the new version is added. It works this way for execution efficiency and safety. Hence the size increase and why the pack operation restored the file to about its original size.

    ------------------------------
    Steven Mann
    Pitney Bowes Software Pty Ltd
    Macquarie Park
    ------------------------------

    Original Message