Format Overview
JSON
+2 Credits
- Web applications
- APIs and microservices
- JavaScript/Node.js projects
- Mobile app backends
NDJSON
+2 Credits
- Streaming and ETL pipelines
- Line-by-line processing
- Bulk loading (BigQuery, Elasticsearch)
- Append-only data logs
CSV
+3 Credits
- Spreadsheet analysis
- Data science workflows
- Excel/Google Sheets
- BI tools and dashboards
Excel
+4 Credits
- Multi-sheet .xlsx workbooks
- Business and reporting
- Offline analysis (Sheets, Calc)
- No-code sort, filter, pivot
Markdown
+3 Credits
- Documentation and READMEs
- Wikis and knowledge bases
- Pull-request summaries
- Human-readable tables
XML
+2 Credits
- Enterprise systems
- SOAP APIs
- Legacy system integration
- Configuration files
YAML
+2 Credits
- Configuration files
- DevOps and CI/CD
- Documentation
- Human-readable data
MySQL
+4 Credits
- MySQL / MariaDB imports
- Full schema with indexes
- Foreign key constraints
- Production-ready DDL
PostgreSQL
+5 Credits
- PostgreSQL-specific DDL
- Type inference and indexes
- Constraints and check rules
- PostGIS compatible
SQLite
+5 Credits
- Embedded and mobile apps
- Single-file database
- Lightweight deployments
- Zero-config setup
SQL Server
+5 Credits
- Microsoft SQL Server DDL
- T-SQL compatible
- Enterprise deployments
- Azure SQL ready
MongoDB
+4 Credits
- NoSQL document store
- Flexible schema queries
- mongorestore compatible
- Aggregation pipeline ready
GeoJSON
+4 Credits
- Mapping and GIS
- Spatial queries
- Map libraries (Mapbox, Leaflet)
- Compatible with PostGIS
PostgreSQL, SQLite, and SQL Server produce dialect-specific DDL with type inference, indexes, and constraints. MySQL produces a full schema with foreign keys and indexes. All SQL formats are ready-to-import.
JSON Format (+2 Credits)
The most popular format for modern web development. Perfect for APIs, web applications, and mobile backends.- Structure & Examples
- Integration Examples
- Best Practices
Clean, nested structure with logical grouping:Multi-dataset structure:
Sample Countries Export
Countries + States Export
CSV Format (+3 Credits)
Perfect for spreadsheet analysis, data science workflows, and business intelligence tools.- Structure & Format
- Excel Integration
- Python/Pandas Usage
Clean, standardized CSV with headers:Multi-sheet structure for combined datasets:
Countries Export
countries.csv
states.csv
XML Format (+2 Credits)
Ideal for enterprise systems, SOAP APIs, and legacy system integrations that require structured, schema-validated data.- Structure & Schema
- Enterprise Integration
- XPath Queries
Well-formed XML with proper namespaces:
Countries Export
YAML Format (+2 Credits)
Human-readable format perfect for configuration files, documentation, and DevOps workflows.- Structure & Format
- Configuration Usage
- Application Integration
Clean, hierarchical YAML structure:
Countries Export
SQL Format (+4 Credits, dialects +5)
Ready-to-execute SQL statements for direct database imports, perfect for production deployments and data migrations.- Generated SQL Structure
- Database Integration
- Application Integration
Complete database schema with relationships:
Countries & States Export
MongoDB Format (+4 Credits)
Amongodump-compatible BSON/JSON export ready to load directly into MongoDB using mongorestore or mongoimport.
- Structure & Examples
- Import & Query
Document structure for countries:Nested states export:
Sample Countries Export
Countries with States
GeoJSON Format (+4 Credits)
GeoJSON is a standard format for encoding geographical data structures. Each city or region is exported as a GeoJSONFeature with coordinates and properties, making it directly usable with mapping libraries and spatial databases.
- Structure & Examples
- Integration Examples
FeatureCollection for cities:
Sample GeoJSON Export
Coordinates follow the GeoJSON standard:
[longitude, latitude] (not [latitude, longitude]). The coordinate reference system is WGS 84 (EPSG:4326).Format Selection Guide
Choosing the right format can save you credits and development time. Use this decision tree:Define Your Use Case
Ask yourself:
- Where will this data be used?
- Who will consume the data?
- What tools do you have available?
- Do you need real-time updates?
Consider Integration Complexity
Development Time vs Credit Cost:
Web Applications & APIs
Web Applications & APIs
Recommendation: JSON (+2 credits)
- Native JavaScript support
- Easy API integration
- No additional parsing needed
- Perfect for React, Vue, Angular
Data Analysis & BI
Data Analysis & BI
Recommendation: CSV (+3 credits)
- Excel/Google Sheets ready
- Pandas compatibility
- Tableau/PowerBI import
- Statistical analysis tools
Enterprise Systems
Enterprise Systems
Recommendation: XML (+2 credits)
- Schema validation
- SOAP web services
- Legacy system integration
- Structured data requirements
Configuration & DevOps
Configuration & DevOps
Recommendation: YAML (+2 credits)
- Human-readable format
- Kubernetes configs
- CI/CD pipelines
- Documentation-friendly
Database Population
Database Population
Recommendation: SQL (+4 credits) or PostgreSQL/SQL Server/SQLite3 (+5 credits)
- Direct database import
- Proper relationships
- Production-ready
- Migration-friendly
Best Practices by Format
- JSON Optimization
- CSV Best Practices
- SQL Production Tips
Performance Tips:Memory Management:
Lazy Loading
Efficient Processing
NDJSON Format (+2 Credits)
NDJSON (Newline-Delimited JSON) writes one JSON object per line with no enclosing array, so each line is an independent, fully-valid JSON record. This makes it ideal for streaming, append-only logs, and big-data tools that process input line by line without loading the whole file into memory.When to use NDJSON
Streaming & ETL
Process records one line at a time in data pipelines without buffering the entire dataset in memory.
Bulk loading
Feed warehouses and search engines (BigQuery, ClickHouse, Elasticsearch) that natively accept newline-delimited JSON.
Markdown Format (+3 Credits)
The Markdown export renders your selected data as GitHub-flavoured Markdown tables — one table per dataset, with a header row and one row per record. It is meant for documentation, READMEs, wikis, and pull-request descriptions where the data needs to be readable at a glance without any extra tooling.When to use Markdown
Documentation
Drop ready-made tables into READMEs, wikis, or Mintlify / Docusaurus pages.
Reports & PRs
Share a quick, readable snapshot of geographical data in issues, pull requests, or notes.
Excel Format (+4 Credits)
The Excel export produces a native.xlsx workbook — a binary spreadsheet with one worksheet per dataset (Countries, States, Cities), a bold header row, and sensible column widths. It opens directly in Microsoft Excel, Google Sheets, LibreOffice Calc, or Numbers with no import step.
When to use Excel
Business & reporting
Hand a polished, multi-sheet workbook to analysts and stakeholders who live in spreadsheets.
Offline analysis
Sort, filter, pivot, and chart geographical data without writing any code.
Need help choosing a format? Consider your primary use case:
- Quick prototyping: Start with JSON for web apps
- Data analysis: Use CSV for spreadsheet compatibility
- Production database: Invest in SQL for proper setup
- Configuration management: YAML for readability
- Streaming & big data: Use NDJSON for line-delimited records
View Pricing
See detailed pricing for all formats and credit packages