Boost Your MapInfo Workflow with PolyNodeExtractor: Tips & Best Practices

PolyNodeExtractor for MapInfo: From Polygons to Node Tables in Minutes

Converting polygon features into node (vertex) tables is a common GIS task for analysis, topology checks, and data conversion. PolyNodeExtractor for MapInfo streamlines that process, letting you extract polygon vertices into a point table quickly and reliably. This article explains what PolyNodeExtractor does, when to use it, a concise step-by-step workflow, useful options, and tips for clean, ready-to-use node tables.

What PolyNodeExtractor does

• Converts polygon (region/multipolygon) features into a point layer where each point represents a polygon vertex.
• Preserves polygon identifiers so extracted nodes can be linked back to their source polygons.
• Optionally retains vertex order and part indices for multipart polygons.
• Exports attributes (selected or all) from polygons to the node table for downstream joins and analysis.

When to use it

• Preparing vertex-level datasets for network analysis, buffering, or snapping.
• Creating topology checks (e.g., detecting repeated vertices, collinear points).
• Converting polygon boundaries into node-based representations for export or CAD use.
• Extracting vertices to generate labels at corner points or to measure per-vertex attributes.

Quick step-by-step: Extract nodes in minutes

1. Open MapInfo and load the map table containing the polygon layer.
2. Launch PolyNodeExtractor from the Tools/Extensions menu (or run the supplied script).
3. Select the polygon layer as the source.
4. Choose an output table name and location for the node table (new .TAB/.MIF or existing table).
5. Set options:
   • Include attributes: choose which polygon fields to copy.
   • Preserve order: enable if you need vertex sequence or to rebuild parts.
   • Include part index: enable for multipart polygons (part number per vertex).
   • Skip duplicate/consecutive identical vertices: enable to remove redundant points.
6. Run extraction. Typical run time: seconds to minutes depending on dataset size.
7. Open the resulting node table. Verify fields: geometry (point), source polygon ID, vertex index, part index (if selected), and copied attributes.
8. (Optional) Create spatial index on the node table for faster spatial queries.

Key options and what they mean

• Preserve vertex order: keeps the original ordering so vertices can be reassembled into lines/polygons later.
• Vertex index: sequential number of the vertex within its polygon (useful for sorting).
• Part index: indicates which polygon part a vertex belongs to (for multipart shapes).
• Attribute copy list: smaller attribute sets speed processing and reduce table size.
• Merge duplicates: removes exact duplicate points; helpful after topological cleaning.

Common uses and workflows

• Topology checks: export nodes, then run queries to find overlapping or duplicated nodes.
• Boundary labeling: place labels at vertices by joining node attributes to labeling rules.
• CAD export: export node table to MIF/DXF to provide exact vertex coordinates for CAD workflows.
• Geoprocessing scripts: call PolyNodeExtractor in batch to process many tables and feed downstream analysis.

Tips for clean results

• Clean source polygons first: remove slivers and snap small gaps to reduce unnecessary vertices.
• Limit copied attributes to those you need to keep output compact.
• If working with projected coordinates, ensure the table projection is correct before extraction to preserve accurate coordinates.
• For very large datasets, run extraction on clipped tiles and then merge node tables