{
    "@context": {
        "schema": "https://schema.org/",
        "dct": "http://purl.org/dc/terms/",
        "hg": "https://hormuz.group/data/ns#"
    },
    "id": "hg:infrastructure:qom-logistics-hub",
    "identifier": "hg:infrastructure:qom-logistics-hub",
    "dataset_type": "entity_dataset",
    "entity_type": "infrastructure",
    "data_version": "2.0",
    "generated_by": "Hormuz Data Layer 0.2.1",
    "generated_at": "2026-07-04T02:51:18+00:00",
    "name": "Qom Logistics Hub",
    "slug": "qom-logistics-hub",
    "status": "publish",
    "url": "https://hormuz.group/infrastructure/qom-logistics-hub/",
    "json_url": "https://hormuz.group/wp-content/uploads/hormuz-data/cpt/infrastructure/qom-logistics-hub.json",
    "rest_url": "https://hormuz.group/wp-json/hormuz-data/v1/cpt/infrastructure/qom-logistics-hub",
    "summary": "",
    "machine_summary": "Qom Logistics Hub Qom Logistics Hub matters in the Hormuz Graph because Qom sits on one of Iran’s most important central road corridors, between Tehran, Isfahan, Arak, Kashan, and southern routes. Its role connects road freight, warehousing, pilgrimage-related consumption, industrial distribution, and capital-region supply chains without the congestion profile of Tehran. The asset is relevant for understanding how goods move through central Iran, where Qom can function as a consolidation, redistribution, and service point for companies serving both Tehran’s demand base and central industrial markets. Qom Logistics Hub Qom, Qom Province, Iran province: Qom industry: Logistics & Transport, Road Freight, Warehousing market: Enterprise Demand, Supply Chains, Trade & Transit, Transport challenges: Data Gaps, Logistics Gap, Transport Gap infrastructure_type: Logistics Hub city: Qom",
    "published_at": "2026-06-24T12:54:14+00:00",
    "modified_at": "2026-06-24T12:54:14+00:00",
    "taxonomies": {
        "province": [
            {
                "id": 199,
                "name": "Qom",
                "slug": "qom",
                "url": "https://hormuz.group/provinces/qom/"
            }
        ],
        "industry": [
            {
                "id": 19,
                "name": "Logistics & Transport",
                "slug": "logistics-transport",
                "url": "https://hormuz.group/industry/logistics-transport/"
            },
            {
                "id": 115,
                "name": "Road Freight",
                "slug": "road-freight",
                "url": "https://hormuz.group/industry/logistics-transport/road-freight/"
            },
            {
                "id": 118,
                "name": "Warehousing",
                "slug": "warehousing",
                "url": "https://hormuz.group/industry/logistics-transport/warehousing/"
            }
        ],
        "market": [
            {
                "id": 40,
                "name": "Enterprise Demand",
                "slug": "enterprise-demand",
                "url": "https://hormuz.group/market/enterprise-demand/"
            },
            {
                "id": 76,
                "name": "Supply Chains",
                "slug": "supply-chains",
                "url": "https://hormuz.group/market/enterprise-demand/supply-chains/"
            },
            {
                "id": 39,
                "name": "Trade & Transit",
                "slug": "trade-transit",
                "url": "https://hormuz.group/market/trade-transit/"
            },
            {
                "id": 78,
                "name": "Transport",
                "slug": "transport",
                "url": "https://hormuz.group/market/public-projects/transport/"
            }
        ],
        "challenges": [
            {
                "id": 187,
                "name": "Data Gaps",
                "slug": "data-gaps",
                "url": "https://hormuz.group/challenges/operational-risks/data-gaps/"
            },
            {
                "id": 170,
                "name": "Logistics Gap",
                "slug": "logistics-gap",
                "url": "https://hormuz.group/challenges/infrastructure-gaps/logistics-gap/"
            },
            {
                "id": 169,
                "name": "Transport Gap",
                "slug": "transport-gap",
                "url": "https://hormuz.group/challenges/infrastructure-gaps/transport-gap/"
            }
        ],
        "infrastructure_type": [
            {
                "id": 317,
                "name": "Logistics Hub",
                "slug": "logistics-hub",
                "url": "https://hormuz.group/infrastructure-type/logistics-hub/"
            }
        ],
        "city": [
            {
                "id": 373,
                "name": "Qom",
                "slug": "qom",
                "url": "https://hormuz.group/cities/qom/"
            }
        ]
    },
    "taxonomy_labels": {
        "province": "Qom",
        "industry": "Logistics & Transport, Road Freight, Warehousing",
        "market": "Enterprise Demand, Supply Chains, Trade & Transit, Transport",
        "challenges": "Data Gaps, Logistics Gap, Transport Gap",
        "infrastructure_type": "Logistics Hub",
        "city": "Qom"
    },
    "fields_summary": {
        "official_name": "Qom Logistics Hub",
        "city_location": "Qom, Qom Province, Iran",
        "strategic_role": "Qom Logistics Hub matters in the Hormuz Graph because Qom sits on one of Iran’s most important central road corridors, between Tehran, Isfahan, Arak, Kashan, and southern routes. Its role connects road freight, warehousing, pilgrimage-related consumption, industrial distribution, and capital-region supply chains without the congestion profile of Tehran. The asset is relevant for understanding how goods move through central Iran, where Qom can function as a consolidation, redistribution, and service point for companies serving both Tehran’s demand base and central industrial markets.",
        "operational_status": "active",
        "related_use_cases": "Useful for route selection, warehouse-location screening, road-freight planning, central Iran distribution strategy, partner search, and comparison of logistics alternatives around Tehran, Qom, Kashan, and Isfahan. Analysts can use it to assess whether Qom can reduce delivery friction or support regional stockholding. Due diligence should verify facility quality, trucking access, land availability, labor, road congestion, and actual tenant or operator depth."
    },
    "fields": {
        "rank_math_internal_links_processed": "1",
        "wp_statistics_words_count": "0",
        "official_name": "Qom Logistics Hub",
        "city_location": "Qom, Qom Province, Iran",
        "operational_status": "active",
        "verification_status": "basic",
        "data_confidence": "medium",
        "last_updated": "24/06/2026",
        "strategic_role": "Qom Logistics Hub matters in the Hormuz Graph because Qom sits on one of Iran’s most important central road corridors, between Tehran, Isfahan, Arak, Kashan, and southern routes. Its role connects road freight, warehousing, pilgrimage-related consumption, industrial distribution, and capital-region supply chains without the congestion profile of Tehran. The asset is relevant for understanding how goods move through central Iran, where Qom can function as a consolidation, redistribution, and service point for companies serving both Tehran’s demand base and central industrial markets.",
        "related_use_cases": "Useful for route selection, warehouse-location screening, road-freight planning, central Iran distribution strategy, partner search, and comparison of logistics alternatives around Tehran, Qom, Kashan, and Isfahan. Analysts can use it to assess whether Qom can reduce delivery friction or support regional stockholding. Due diligence should verify facility quality, trucking access, land availability, labor, road congestion, and actual tenant or operator depth.",
        "source_note": "Based on public infrastructure, provincial, industrial, and market-context information. Further verification is required before treating this profile as verified investment intelligence.",
        "rank_math_analytic_object_id": "11"
    },
    "field_profile": {
        "rank_math_internal_links_processed": {
            "type": "string",
            "present": true,
            "length": 1
        },
        "wp_statistics_words_count": {
            "type": "string",
            "present": true,
            "length": 1
        },
        "official_name": {
            "type": "string",
            "present": true,
            "length": 17
        },
        "city_location": {
            "type": "string",
            "present": true,
            "length": 23
        },
        "operational_status": {
            "type": "string",
            "present": true,
            "length": 6
        },
        "verification_status": {
            "type": "string",
            "present": true,
            "length": 5
        },
        "data_confidence": {
            "type": "string",
            "present": true,
            "length": 6
        },
        "last_updated": {
            "type": "string",
            "present": true,
            "length": 10
        },
        "strategic_role": {
            "type": "string",
            "present": true,
            "length": 593
        },
        "related_use_cases": {
            "type": "string",
            "present": true,
            "length": 462
        },
        "source_note": {
            "type": "string",
            "present": true,
            "length": 186
        },
        "rank_math_analytic_object_id": {
            "type": "string",
            "present": true,
            "length": 2
        }
    },
    "sources": [
        {
            "type": "note",
            "value": "Based on public infrastructure, provincial, industrial, and market-context information. Further verification is required before treating this profile as verified investment intelligence."
        }
    ],
    "quality": {
        "required_fields": [
            "official_name",
            "city_location",
            "strategic_role",
            "operational_status",
            "related_use_cases",
            "verification_status",
            "data_confidence",
            "source_note",
            "last_updated"
        ],
        "missing_required_fields": [],
        "missing_required_count": 0,
        "verification_status": "basic",
        "data_confidence": "medium",
        "last_updated": "24/06/2026",
        "stale_over_180_days": false,
        "quality_score": 100
    },
    "verification": {
        "verification_status": "basic",
        "data_confidence": "medium",
        "last_updated": "24/06/2026"
    }
}