<?xml version="1.0"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="432695" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="28/10/2026" />
        <classifier id="PublicationName" value="DailyStar" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="285,108,972,909" />
         <classifier id="Layer" value="Layer 1"/>
          <classifier id="numcol" value="4"/>
         <classifier id="ArticleStyle" value=""/>
       <classifier id="Epaper-Build" value="7.1.5.2"/>
  <classifier id="ProcessingDateTime" value="Wed Oct 28 2026 08:15:03 GMT+0600"/>
      </identified-content>

      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="DailyStar" date.publication="20261028T000000+5.30" edition.name="Dhaka Edition" edition.area="MAI" position.section="DST28102606MAI-Editorial" position.sequence="6" ex-ref="DST28102606MAI-Editorial.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
<body.head>
      <hedline>
    	<hl1 id="Headline1" ul="0" ol="0" ulColor=""  ulWeight=""  olColor=""  olWeight="" textFrameColor="" orgstyle="[No Paragraph Style]" class="1" MainHead="true" style="Headline1">
		<lang class="3" colour="#000000" orgstyle="[No Paragraph Style]" style="Headline1"  font="Antonia H1" fontStyle="Bold" size="45">Infrastructure alone will not fix Chattogram’s mobility problem </lang>
	</hl1>

       </hedline>
</body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
     <block>
	<media id="1" media-type="image">
		<media-reference id="tn" source-credit="" data-location="1" source="ImageOfFrame38906_6_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
<media-reference id="tn" source-credit="" data-location="1" source="ImageOfFrame38802_6_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
<media-reference id="tn" source-credit="" data-location="3" source="72ddFARZANA_ISL_6_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
<media-reference id="tn" source-credit="" data-location="4" source="ED_1__Shahid_Wa_6_MAI_tn.jpg"  Units="pixels" width="50" height="50"></media-reference>
	</media>
</block>

     <p style=".Bodylaser" ul="0" ol="0"  orgstyle="INDENTLESS BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="INDENTLESS BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The quality of a city’s governance is reflected in how easily its residents can move within its jurisdiction. Chattogram, the commercial capital and second largest economic hub of Bangladesh, feels like an abandoned city because of poor mobility and low safety standards. But it was not always like this. The city’s urban infrastructure was once shaped by hills, canals, and arterial corridors. It allowed people to move through the city not systematically but with relative ease and predictability. The comparatively narrow roads were reinforced by the surrounding land use, and organic canals and drainage channels supported flood management. This “arrangement” was not efficient by modern transport standards, but it worked well enough to sustain the city as the country’s growing commercial hub.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Today, moving through Chattogram often means sitting in traffic, navigating disconnected roads, and feeling unsafe amid congestion and chaos. That cities will expand is inevitable, but this dysfunctionality only indicates an institutional neglect towards developing an integrated transport system as the city grew. 
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Over the past decade, Chattogram has witnessed mega infrastructure projects like flyovers, an elevated expressway, highways, and major expansion of the existing roads. While some of them were needed for better connectivity, all of them were built without developing an end-to-end ecosystem to ensure smooth functionality. Flyovers were built with flawed designs, including unsafe curves, and without operational feeder roads. The expressway was built and opened for public use three years ago with all nine of its access ramps inaccessible; only six ramps were recently opened for use while the rest are expected to be accessible in two months. Meanwhile, roads have been expanded without keeping the drainage system in mind. 
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">In all these mega infrastructures, one common aspect has been missing from consideration: public movement. The Chattogram Development Authority (CDA) has undertaken 10 development projects worth more than Tk 14,874 crore, including six transport projects involving road widening, new road connections, an outer ring road extension, and the proposed Oxygen Moar flyover. But what is the city’s mobility strategy connecting these individual projects? The Oxygen-Quwaish development project carries a proposed cost of Tk 2,024 crore. The issue of concern here is not whether the intersection needs intervention but whether another flyover or wider roads will resolve the underlying causes of congestion. This also raised an unexamined but important policy question: what problems have flyovers and expressways actually solved in Chattogram? 
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">According to urban transport planning principles, elevated roads can function properly only when they are embedded within an integrated transport system: a clear traffic hierarchy, well-planned access corridors, reliable public transit, and safe pedestrian infrastructure. These preconditions were not all applied while implementing these grade-separated roads. Not only were the designs of these flyovers flawed, but the intersections and roads underneath were not rebuilt keeping both humans and vehicles in mind. No wonder that the traffic congestion did not just trouble the junctions but also all the access and exit points, as well as the surface roads under the flyovers. The elevated expressway followed a similar pattern, prioritising speed over safety, ignoring traffic demand analysis and public transport integration, and enabling the construction of unplanned ramps. The consequences were not surprising: fatal crashes due to high speed on the upside and clogged roads below.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">These infrastructures may improve travel time for a limited group of users, but do little to improve the overall mobility. Pedestrians, who are major stakeholders, were excluded from all planning considerations, and footpaths became fragmented, leading to open drains. Also, despite earlier planning recommendations, the movement of freight to and from the Chattogram Port remains a significant challenge for the city’s transport network. The port-bound trucks and industrial vehicles share road space with local traffic, resulting in congestion and delays that affect both urban mobility and economic efficiency. In a port city where the majority of daily trips are short, mixed-mode, and human-centred, shouldn’t large infrastructure investment be evaluated by how effectively they integrate freight corridors, truck terminals, port access, public transport, and safe pedestrian movement into a coordinated citywide mobility strategy?
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The frustrating part is that Chattogram has not lacked transport assessments or planning recommendations. Earlier studies supported by the Japan International Cooperation Agency (JICA), alongside government masterplans, identified weak coordination between agencies, inadequate traffic demand analysis, and the absence of an effective citywide multimodal transport framework. More recently, the CDA’s draft Chattogram Metropolitan Master Plan 2025-2050 has proposed an integrated transport system combining modern buses, commuter rail and water buses, alongside improved terminals, traffic signals and parking management. It also recognises that congestion cannot be solved by increasing road capacity alone. But a master plan’s value does not lie in what it proposes on paper. Individual investments should be prioritised, designed and implemented in accordance with its wider vision. To fully implement the master plan, the megaprojects and the proposed public transport network, freight management and pedestrian infrastructure must complement each other.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Successful cities around the world have shifted their policies from car-centric expansion to integrated spatial mobility solutions that prioritise public transport, pedestrian-friendly infrastructure, freight efficiency, and traffic demand management. Cities like Copenhagen, Oslo, and Rotterdam have recognised that urban competitiveness depends on how reliably people and goods can move. To correct its course, Chattogram needs a fundamental policy shift from speed and construction to safety, accessibility and coordination. Doing so requires asking difficult questions about past investments and whether the port city needs more mega infrastructure or better administrative policy movement. Until those questions are answered honestly, the city will continue to build without planning, and despite decades of investment, mobility here will continue to suffer.
</lang>
</p>

    </body.content>
  </body>
</nitf>