Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Deprecated: Use of "parent" in callables is deprecated in /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php on line 501

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769

Warning: Cannot modify header information - headers already sent by (output started at /project/VIDEV/web/app/plugins/simple-lightbox/includes/class.options.php:501) in /project/VIDEV/web/wp/wp-includes/rest-api/class-wp-rest-server.php on line 1769
{"id":29750,"date":"2020-08-09T08:23:52","date_gmt":"2020-08-09T06:23:52","guid":{"rendered":"https:\/\/vosgesinfo.fr\/remiremontinfo\/2020\/08\/comite-secheresse-reactions-associations\/"},"modified":"2020-08-09T08:23:52","modified_gmt":"2020-08-09T06:23:52","slug":"comite-secheresse-reactions-associations","status":"publish","type":"post","link":"https:\/\/vi.si-developpement.fr\/remiremontinfo\/2020\/08\/comite-secheresse-reactions-associations\/","title":{"rendered":"Comit\u00e9 S\u00e9cheresse – r\u00e9actions des associations"},"content":{"rendered":"

Comme en 2018 et 2019, le pr\u00e9fet a pris des arr\u00eat\u00e9s de restriction d\u2019usage de l\u2019eau suite \u00e0 la r\u00e9union du comit\u00e9 s\u00e9cheresse. Cette ann\u00e9e, au motif invoqu\u00e9 du COVID, les membres du comit\u00e9 s\u00e9cheresse ont \u00e9t\u00e9 sollicit\u00e9s fin juin par voie d\u00e9mat\u00e9rialis\u00e9e. L\u2019ASVPP et VNE ont particip\u00e9 activement en envoyant plusieurs questions et propositions. Le 9 juillet le pr\u00e9fet a r\u00e9uni un comit\u00e9 restreint en pr\u00e9sentiel<\/strong> duquel les associations de protection de l\u2019environnement, contrairement \u00e0 la f\u00e9d\u00e9 de p\u00eache, ont \u00e9t\u00e9 exclues. L\u2019absence de d\u00e9bat (cf CR) sur les questions soulev\u00e9es, et bien s\u00fbr de r\u00e9ponse \u00e0 ce jour, nous am\u00e8ne \u00e0 penser que les probl\u00e8mes soulev\u00e9s et propositions \u00e9taient particuli\u00e8rement\u00a0 g\u00eanants et que la situation sanitaire a servi de pr\u00e9texte pour les \u00e9vacuer.<\/em><\/p>\n

Nous avions en effet soulev\u00e9, la question de l\u2019in\u00e9galit\u00e9 des usagers face aux restrictions d\u2019usages. Comment justifier des restrictions d\u2019usages aux citoyens de Vittel-Contrex mais pas aux industriels alors qu\u2019ils pr\u00e9l\u00e8vent dans la m\u00eame nappe\u00a0!<\/em><\/p>\n

Nous avons \u00e9voqu\u00e9 pour la 3\u00e8me ann\u00e9e cons\u00e9cutive, l\u2019absence de donn\u00e9e concernant la surveillance de l\u2019\u00e9volution du niveau de la nappe des Muschelkalk, ce qui ne permet pas au pr\u00e9fet de prendre des mesures de restriction qui s\u2019imposent \u00a0le cas \u00e9ch\u00e9ant (cours d\u2019eau en assec comme le petit Vair) vis \u00e0 vis de l\u2019usager quasi exclusif Nestl\u00e9 Waters\u00a0! Comment un seul pi\u00e9zom\u00e8tre public, du c\u00f4t\u00e9 d\u2019Har\u00e9ville, peut \u2013il \u00eatre significatif de l\u2019impact des\u00a0 nombreux pr\u00e9l\u00e8vements autour de Vittel et Contrex\u00e9ville\u00a0? Comment accepter que l\u2019Etat, responsable du suivi des nappes, n\u2019exige pas de Nestl\u00e9 la communication en temps r\u00e9el de l\u2019\u00e9volution du niveau de la nappe pour chacun de ses forages, et soit en mesure de les v\u00e9rifier\u00a0! L\u00e0 encore pas de trace de cette question dans le CR, et aucune r\u00e9ponse du pr\u00e9fet\u00a0!<\/em><\/p>\n

La question de l\u2019exploitation des microcentrales a \u00e9t\u00e9 signal\u00e9e, \u00e0 cause de l\u2019impact sur les \u00e9tiages des cours d\u2019eau en t\u00eate de bassin tr\u00e8s affect\u00e9s par la s\u00e9cheresse avec une demande de renforcement des contr\u00f4les de pratiques qui enfreignent la r\u00e9glementation.<\/em><\/p>\n

Nous avons aussi rebondi sur les difficult\u00e9s v\u00e9cues par les agriculteurs concernant l\u2019approvisionnement en\u00a0 fourrages, par trois propositions\u00a0:<\/em><\/p>\n