ioda-net/geo-front3

frontend from geoadmin/mf-geoadmin3

geo-front3's Issues

Fix background layers

Improve the deployment process

Currently, we must load the conf with . rc_jenselme and then launch make. A single command would be more usefull. Proposal:

• Create a rc_deploy config file not tracked by git
• Create a script that loads this file and then passes all its argument to make

Print grid

Require the correct layer in the configuration of mapserver from @tigerfoot

Print coords of a corner: should I add a frame to the map?

gulp dev --portal doesn't respect portal | need to work like mapinfra/bin

if gulp dev --portal n16 is run all generated files goes to dev/geojb
:-(

Need a fix à la mapinfra
To be done in conjunction with @Jenselme

Voir apparaître la valeur de l'échelle de visualisation

• 1/500
• 1/2000
• 1/510
• …

Modify an element of a drawing causes the layer to be duplicated

Preserve transparency when printing

Deployment to production

All the required files are in the prd folder. I initially suggested using rsync to deploy but this poses the problem of how to revert to a previous version if needed. The solution I see are:

• build the prod version on the prod server: this implies to have all the dependencies (git, node, npm, python3 + mako) and the deployment will require some time. We can use something similar to the api3 with git tags to revert/deploy new version.
• Use a basic rsync but we cannot easily revert.
• Put the content of prd we want to deploy in a folder named after the timestamp. Then rsync the content of the prd folder on the production server with the content of this folder. Once again, we can use something similar to want we are doing in the deployment of the API except that we are using rsync instead of git. It seems similar to want swisstopo does with its snapshot deployment.
• Track the prd folder with git (a subrepo of the parent project would be the way to go). It has the advantages of being flexible and simple. Moreover, we can use something similar to the api deployment. It should not take much disk space since all data are compressed by git and it doesn't contain that much images.

I prefer the last solution: simple, flexible, close to what I proposed for the API.

Use new configuration from mapinfra

• catalog
• layers config
• services
• layer search
• search: search is topic by topic and uses the database.

Choose title for print

Save to owncloud

Improve error messages

Use the default title provide by capabilities.json when printing

Print external layers

Print point

Automatically desactivate click for feature if feedback is in use

Trying to draw something during a feedback report activate feedback table

How to handle efficiently external stats tools

Actually without any changes we wrongly use key of swisstopo

 <!-- verification for google webmaster tools -->
    <meta name="google-site-verification" content="ZAmW5d4_2X8xb5Yy_nYQbnTSe1EIeSqyhox9aXXwrws"/>
    <!-- verification for bing webmaster tools -->
    <meta name="msvalidate.01" content="58E0E0B7DD4AB3D30EE315C695950E68"/>
    <!-- verification for yandex webmaster tools -->
    <meta name='yandex-verification' content='4795f82c05657028'/>

Seems the best way to solve this would be to have variables.
We would have to talk about it with swisstopo

WMTS import

Not yet supported, tested with http://wmts.geo.admin.ch/1.0.0/WMTSCapabilities.xml

indentify : don't crash if api answer 404

To be checked, filter out 404 results

Print legend with pdf

HTTPS and inclusion from layer from other WMS

Improve the translation script

It should fetch the new translations from swisstopo spreadsheet and then accept any number of CSV and replace the key accordingly (and in order).

Print lines with line style, not polygon

Print coords of a corner: should the coords be updated in function of the projection?

Fix tests

Get feature: must use a unique id in track by for ng-repeat

Complete cleaning of repo

Some files are not useful to us. The remaining files must be removed.

Feature handle double objects

In some case data are stored in the same view table ( like PF) but are spread on the map in 2 distincts layers.
Result the point is shown 2 times.

to be analyzed : should we split the view like the mapserver layer is ? <- @verogis

Insure that an object is stored and shown only once in feature results <- @Jenselme

Reference on map http://api.disney.interne/shorten/6670932030

Print imported KML

Make topic use images again instead of sprites

Add an option in the translation script to support languages

Without it, all languages for Swisstopo will be generated. This is not what we want. We should be able to select the languages.

NB: currently, when we import translations from Swisstopo, we must delete the unnecessary columns.

Update deployment process for multiple portals

We must give an argument to gulp so it generates the frontend for one portals in the correct folder: dev/portalname or prd/portalname.

Missing primary key on tables in schema features

@verogis PK are required. Can you add them please?

Repair print of features

Switch from mobile to desktop fails

Features : grid sorting and highlight

Here the copy and paste about JBR remark
Procédures

• zoom parcelles
• sélection plusieurs parcelles
• cool le bandeau en-bas avec les attributs
• on passe la souris sur les lignes, ça illumine les objets sur la carte, cool, ça marche
• on trie les données selon le numéro de parcelle
• on passe la souris sur les lignes, ça illumine les objets sur la carte, pas cool,
  c'est pas la bonne parcelle....

Je te joins un endroit où il y a quelques parcelles évidentes à trouver.

http://geojb/?topic=03_cds&lang=fr&X=227523.13&Y=579176.00&zoom=8&bgLayer=voidLayer&catalogNodes=&layers=COUVERTUREDUSOL,CDS_SYMBOLE,COUVERTUREDUSOL_TEXTE,ODEL,ODELPROJET,BATIMENTS,PARCELLE,COUVERTUREDUSOL_LIGNE,PARCELLE_NUMERO,ODEL_TEXTE

C'est confirmer chez moi aussi.

Print measures doesn't work

"Error: cyclic object value
toJson@http://dev.geojb/lib/angular.js:1213:10
$HttpProvider/this.defaults.transformRequest<@http://dev.geojb/lib/angular.js:9397:74
transformData/<@http://dev.geojb/lib/angular.js:9339:12
forEach@http://dev.geojb/lib/angular.js:336:11
transformData@http://dev.geojb/lib/angular.js:9338:3
$http/serverRequest@http://dev.geojb/lib/angular.js:10029:23
processQueue@http://dev.geojb/lib/angular.js:14567:28
scheduleProcessQueue/<@http://dev.geojb/lib/angular.js:14583:27
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://dev.geojb/lib/angular.js:15846:16
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://dev.geojb/lib/angular.js:15657:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://dev.geojb/lib/angular.js:15951:13
done@http://dev.geojb/lib/angular.js:10364:36
completeRequest@http://dev.geojb/lib/angular.js:10536:7
requestLoaded@http://dev.geojb/lib/angular.js:10477:1

Correctly print rotated maps

Repair print of legend

View topic tooltip

Automatic scale selection for print fails if zoom is too close

Add a portal feedback mail config option

This email address will be transmitted to the api.
(the api will fallback is nothing is given)

Add a real subject (and automagically happen the portal name)

Features and languages

Genre must be translated when we change language.

Print text

Print city name

Check with vhe if we can't have a special layers off to get only the label of the city on the map
drawed at a specific location (like bottom left)

Opacity parameter for layers is not taken into account

Print coords of a corner: should the coords be updated in function of the projection

Print the north arrow

Use gulp to generate template

After a study, gulp meets our needs. It must:

• Create CSS files from less source with lessc
• Minify CSS and HTML
• Install JS libs with NPM
• Call closure linter (python): must be installed and then we can use a plugin.
• Call closure compiler
• Clean the project (files to remove)
• Generate files for prod, pserve and dev if the source changed

How to handle translations for various portal?

Currently, our translations are generated from a CSV file which contains all the keys. Only the JSON are tracked by git. But a specific portal may want to override some keys. How to do that?

Proposal: propose 2 CSV, one with all the keys and the other one with the values to override. Both should be tracked by git (instead of the JSON) and depending on the name of the portail, we select the "override" CSV and generate its JSON.