Convert BNA to E00 Online - Free & Fast

What is BNA?

Atlas Boundaries (BNA) is a simple ASCII coordinate format for storing polygon boundary data, originally developed by Atlas GIS for representing area features like postal codes, sales territories, and administrative regions as coordinate lists.

What is E00?

ArcInfo Exchange (E00) is a proprietary interchange format developed by ESRI for exporting and importing Arc/Info coverages, encoding vector topology, attributes, and raster data in an ASCII text file for data migration between GIS systems.

When Should You Use BNA vs E00?

BNA vs E00: Key Differences

• •BNA and E00 diverge on compression: lossy compression for the source, lossy compression for the target.
• •Since both BNA and E00 use lossy compression, the quality characteristics are comparable — differences in file size come down to how efficiently each format implements compression.
• •How transparency is handled: E00 does not support alpha channels — transparent areas in the source will become opaque.
• •Storage footprint: 1KB to 50MB depending on boundary complexity for BNA vs 100KB to several GB depending on coverage complexity for E00.
• •Use case fit: BNA targets atlas gis boundary exchange, regional mapping, legacy spatial data conversion and E00 targets legacy arcinfo data migration, gis archival data recovery — your choice depends on which workflow stage you are serving.

Advantages of BNA

• ✓The lossy nature of BNA means file sizes stay reasonable while handling Atlas GIS boundary exchange, regional mapping, legacy spatial data conversion efficiently.
• ✓From mobile devices to enterprise servers, BNA is recognized and supported everywhere.
• ✓Storage and bandwidth costs drop significantly when using BNA thanks to its efficient compression.
• ✓BNA is a first-class citizen in all major software ecosystems, from creative suites to development environments.

Advantages of E00

• ✓At its core, E00 relies on lossy encoding — a design choice that makes it perfect for Legacy ArcInfo data migration, GIS archival data recovery.
• ✓You won't run into compatibility issues with E00 — it's a universal standard across platforms.
• ✓File size management with E00: aggressive compression with minimal visible quality loss.
• ✓Every major application in the Legacy ArcInfo data migration, GIS archival data recovery space supports E00 natively.

Common Use Cases for BNA to E00 Conversion

Industry Applications

Best Practices for BNA to E00 Conversion

• →When converting BNA to E00: confirm the coordinate reference system (CRS / projection) is preserved or explicitly reprojected
• →Keep attribute tables and feature metadata intact — E00 should retain all fields from BNA
• →Check geometry types (point, line, polygon) map cleanly between the two formats
• →Verify that z/elevation values and topology survive the conversion when working with terrain data
• →Always keep a backup of your original files before converting
• →Choose the appropriate quality settings for your specific use case

Troubleshooting BNA to E00 Conversion

• !Topology errors in the converted E00 → self-intersecting polygons or duplicate vertices may not transfer cleanly between formats
• !The E00 file coordinate values shifted slightly → datums (WGS84 vs NAD83) differ even when the projection looks similar
• !Time field values were corrupted after converting BNA to E00 → date and time field formatting varies across GIS formats
• !Null geometry features appear in the converted E00 → empty or null-shape records in BNA may cause validation errors in some formats

More GIS / Geospatial tools