Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
KEADILAN Perak Persoal Kelulusan Pengeluaran Pasir di Segari – Independent

KEADILAN Perak Persoal Kelulusan Pengeluaran Pasir di Segari

Reading Time: < 1 minute

IPOH, 14 Jan 2022 – KEADILAN Perak mempertikaikan kenyataan oleh syarikat Maegma Minerals Sdn. Bhd. berhubung aktiviti pengorekan pasir di pantai Pasir Panjang dalam daerah Manjung.

Menurut satu kenyataan oleh Ketua Penerangan KEADILAN Perak, Muhammad Arafat yang diedarkan hari ini, KEADILAN mempersoalkan bagaimana status tanah ditukar kepada perindustrian sedangkan dalam Rancangan Fizikal Negara (RFN) kawasan tersebut dikategorikan sebgaia Kawasan Sensitif Alam Sekitar Tahap 1 (KSAS 1).

Tambahan pula, bagaimana syarikat boleh mengumumkan untuk membangunkan sebuah kilang keluli bersepadu di kawasan berkenaan sedangkan RFN telah menyatakan dengan jelas bahawa tidak boleh dibangunkan sebarang kegiatan dan penukaran guna tanah kecuali pelancongan eko yang mempunyai impak rendah, untuk tujuan pendidikan atau penyelidikan.

KEADILAN juga mempersoalkan atas alasan apa yang digunakan mendakwa ia tidak menimbulkan risiko terhadap alam sekitar walhal kerja-kerja pengeluaran pasir yang dijalankan oleh syarikat sudah tentu mengganggu pendaratan penyu di situ dan akan berlaku perubahan struktur fizikal kawasan pantai menyebabkan ia tidak lagi sesuai untuk penyu mendapat dan bertelur di situ.

Arafat dalam pada itu menggesa kerajaan menyiasat untuk mengetahui di mana berlaku kesilapan dalam mengeluarkan kelulusan yang tidak selari dengan RFN dan menetapkan syarat pembangunan yang jelas iaitu hanya untuk pelancongan eko berimpak rendah, pendidikan atau penyelidikan sahaja.

Sebelum ini, sebuah portal dalam talian (bukan portal ini) menerbitkan kenyataan oleh syarikat Maegma Sdn. Bhd. bahawa syarikat memiliki tanah perindustrian di Tanjung Hantu, Segari, Manjung memenuhi segala piawaian ditetapkan bagi kerja-kerja yang dilakukan di kawasan berkenaan.

Syarikat tersebut dalam satu kenyataan menjelaskan, segala kerja-kerja yang dilakukan telah diluluskan oleh pihak berkuasa berkaitan dan bekerjasama rapat dengan agensi tersebut.