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":45114,"date":"2019-11-14T19:03:28","date_gmt":"2019-11-14T18:03:28","guid":{"rendered":"https:\/\/vi.si-developpement.fr\/gerardmerinfo\/2019\/11\/urbanisme-a-gerardmer-etat-lieux-perle-vosges-perd-ecrin\/"},"modified":"2019-11-14T19:03:28","modified_gmt":"2019-11-14T18:03:28","slug":"urbanisme-a-gerardmer-etat-lieux-perle-vosges-perd-ecrin","status":"publish","type":"post","link":"https:\/\/vi.si-developpement.fr\/gerardmerinfo\/2019\/11\/urbanisme-a-gerardmer-etat-lieux-perle-vosges-perd-ecrin\/","title":{"rendered":"Urbanisme \u00e0 G\u00e9rardmer \u2013 \u00c9tat des lieux \u2013 La Perle des Vosges perd son \u00e9crin."},"content":{"rendered":"

Apr\u00e8s la parution de mon article paru dans GI le 4 octobre dernier qui d\u00e9non\u00e7ait l\u2019hyper-urbanisation, l\u2019ensemble des commentaires (\u00e0 l\u2019exception de ceux d\u2019un g\u00e9r\u00f4mois qui se reconnaitra) approuvait mes dires et toutes les personnes avec lesquelles j\u2019ai pu \u00e9changer verbalement m\u2019ont manifest\u00e9 elles aussi leur approbation.<\/em><\/p>\n

La r\u00e9glementation relative \u00e0 l\u2019AVAP (Aire de Mise en Valeur de l\u2019Architecture et du Patrimoine), devenu depuis SPR (Site Patrimoniale Remarquable) a \u00e9t\u00e9 approuv\u00e9e en date du 27 janvier 2015 par le Conseil municipal tout comme le PLU (Plan Local d\u2019Urbanisme) l\u2019a \u00e9t\u00e9 le 18 juin 2015.<\/em><\/p>\n

Ce PLU a \u00e9t\u00e9 l\u00e9galement soumis \u00e0 enqu\u00eate publique, ceci dans le but d\u00e9clar\u00e9 d\u2019informer la population, de recueillir son opinion et ses suggestions avant adoption d\u00e9finitive par nos repr\u00e9sentants \u00e9lus.<\/em><\/p>\n

Si Laurence DENY et moi-m\u00eame avions alors fait part de nos observations aupr\u00e8s du commissaire enqu\u00eateur, avec une pertinence, toute modestie gard\u00e9e, que la vue frappante du bouleversement de notre environnement r\u00e9v\u00e8le aujourd\u2019hui, il serait opportun de consulter le registre d\u2019enqu\u00eate pour connaitre et consid\u00e9rer, avec un regard \u00e9clair\u00e9 par la r\u00e9alit\u00e9, tous les autres avis exprim\u00e9s.\u00a0\u00a0\u00a0\u00a0 \u00a0<\/em><\/p>\n

Cette r\u00e9alit\u00e9, d\u2019un paysage et d\u2019un cadre de vie d\u00e9truits, laisse \u00e0 penser que ce registre n\u2019a pas \u00e9t\u00e9 pris en compte lors de l\u2019\u00e9laboration du PLU approuv\u00e9 ainsi sans vraie concertation.<\/em><\/p>\n

Il est n\u00e9cessaire et urgent de modifier ce PLU comme l\u2019ont fait avec lucidit\u00e9 et courage, soutenus en cela par la majorit\u00e9 de leur administr\u00e9s, les maires des communes de MORZINE et du GRAND BORNAND<\/em><\/p>\n

C\u2019est une des d\u00e9cisions prioritaires que le collectif nouvellement constitu\u00e9\u00a0 GERARDMER PATRIMOINE NATURE (https:\/\/gerardmerinfo.fr\/2019\/11\/collectif-gerardmer-patrimoine-nature-actif\/<\/a>) souhaite voir prise.<\/em><\/p>\n

L\u2019hyper-urbanisation, et plus particuli\u00e8rement des secteurs des coteaux, est la cons\u00e9quence de l\u2019application de r\u00e8gles d\u2019urbanisme trop permissives et dont certaines sont, non seulement contradictoires entre PLU et AVAP, mais inapplicables sur le terrain, ce qui se d\u00e9montre par des non-conformit\u00e9s visibles lors de la r\u00e9alisation des constructions ou \u00e0 leur ach\u00e8vement.<\/em><\/p>\n

Je pense particuli\u00e8rement \u00e0 la r\u00e8gle, principalement applicable dans ces secteurs, limitant \u00e0 1.00 m la hauteur des remblais-d\u00e9blais et des murs de sout\u00e8nement. Il suffit de regarder\u2026<\/em><\/p>\n

Le contr\u00f4le de conformit\u00e9 des travaux n\u2019est pas obligatoire, disposition incoh\u00e9rente de la loi ELAN qui laisse toutefois le choix aux maires quant \u00e0 ordonner ou pas ce contr\u00f4le.<\/em><\/p>\n

Si contr\u00f4le il y a, celui-ci doit se faire dans les 3 mois qui suivent la d\u00e9claration d\u2019ach\u00e8vement des travaux car pass\u00e9 ce d\u00e9lai, les communes n\u2019ont plus aucun recours possible envers les contrevenants.<\/em><\/p>\n

A cela s\u2019ajoute le fait que l\u2019instruction des dossiers de demande de permis de construire ou d\u2019am\u00e9nager se fait avec la consid\u00e9ration que l\u2019engagement du p\u00e9titionnaire a seul valeur de droit.<\/em><\/p>\n

C\u2019est-\u00e0-dire qu\u2019un dossier r\u00e9pondant, dans sa pr\u00e9sentation, aux r\u00e8gles d\u2019urbanisme ne sera pas rejet\u00e9 quand bien m\u00eame l\u2019\u0153il averti des membres de la Commission de l\u2019urbanisme y verrait des incoh\u00e9rences. Quand j\u2019avais \u00e9voqu\u00e9 le sujet lors d\u2019une r\u00e9union en mairie le 28 f\u00e9vrier 2017 en demandant de fa\u00e7on abrupte s\u2019il fallait tricher, il m\u2019avait \u00e9t\u00e9 r\u00e9pondu \u00ab\u00a0c\u2019est du d\u00e9claratif, on ne peut rien faire\u00a0\u2026\u00bb.<\/em><\/p>\n

Ces propos n\u2019engagent que moi mais j\u2019ai connaissance de 2 cas, copie des demandes et plans accept\u00e9s \u00e0 l\u2019appui, o\u00f9 j\u2019affirme qu\u2019il est impossible de ne pas voir la non-concordance de la repr\u00e9sentation graphique pr\u00e9sent\u00e9e par rapport \u00e0 la topographie du terrain et \u00e0 sa relative exig\u00fcit\u00e9.<\/em><\/p>\n

Le 2\u00e8me<\/sup> cas, tr\u00e8s r\u00e9cent, concerne un chantier qui vient de d\u00e9marrer o\u00f9 l\u2019architecte a pris un soin tout particulier \u00e0 faire mention de la hauteur de remblai et sout\u00e8nement sur les plans de fa\u00e7ades alors que son plan masse (plan a\u00e9rien) montre qu\u2019il est impossible de limiter cette hauteur \u00e0 celle, r\u00e9glementaire, de \u00e0 1.00 m.<\/em><\/p>\n

Je parle d\u2019un constat et trouve regrettable qu\u2019un professionnel, garant, \u00e0 mon sens, par sa formation ou vocation de la beaut\u00e9 ou de l\u2019harmonie du paysage en terme de nature et b\u00e2ti, puisse choisir, m\u00eame s\u2019il faut vivre de son m\u00e9tier, de satisfaire l\u2019app\u00e9tit d\u2019investisseurs en trahissant des valeurs et une \u00e9thique revendiqu\u00e9es.<\/em><\/p>\n

Le collectif GERARDMER PATRIMOINE NATURE appelle les g\u00e9r\u00f4mois \u00e0 se mobiliser pour que s\u2019arr\u00eate la destruction de leur bien commun, pour que les atteintes bien visibles d\u00e9j\u00e0 port\u00e9es \u00e0 leur environnement ne s\u2019\u00e9tendent encore\u00a0:<\/em><\/p>\n