geoadmin / mf-chsdi3 Goto Github PK

qu'est-ce qu'il faut mettre dans displayFielName quand il n'y a pas d'attribut dans preview()?
displayFielName doit être renseigné. Pour les couches suivantes, voici l'attribut choisi:
ch.swisstopo.vec25-strassennetz: "objectval"
ch.swisstopo.vec25-uebrigerverkehr: "objectval"

Currently a translated attribution is transferred. This makes that it's quite difficult to add a link on the attribution.
In RE2, we worked with ID, like ch.swisstopo and ch.swisstopo.url which were translated client side. I propose to use the same principle.

comma separated list of layers to auto activate (same as RE2)

In RE2, we had a layers parameter for layers where the technical name is different than the name to be used in wmts/wms requests. In such a case, we would specify the layers parameter in the configuration.

The application then needs to take this parameter to create the request.

See discussion here:
https://groups.google.com/forum/#!msg/re3-dev/zolXq98ljlI/GHZ2NBf8YWMJ

Since serverLayerName is now used

Which supports language
Which supports http & https
Which supports version

Layer:
ch.swisstopo.vec200-transportation-oeffentliche-verkehr
Chaque classe prise séparément (2 autres en commentaire) fonctionne.
Les 3 ensemble, la recherche de l'ID se fait uniquement dans la 1ère table (celle de la 1ère classe...)

Will affect the following services:

• identify (will filter the features for htmlpopup and getfeature services)
• search

Should we think about it at some point?
Or you wanted to do it somewhere else?

I need this service to implement the recenter by id(s).
See https://api.geo.admin.ch/main/wsgi/doc/build/api/faq/index.html?highlight=crosshair#what-mean-the-permalink-parameters <layer bod id> parameter.

What's the best service to use ?

Right now, in our layers service, the sublayers are in a comma separated string. Put it into an array (as in RE2...)

feedback should be added to the RewriteRule in wsgi.conf.in (last line)

In the application, we rely on the fact that the catalog tree returned by the catalogServer service returns the same catalog for every language. Right now, this is not the case.

See [1] and [2] in category category_240

Because this is important, it would make sense to test this with unit tests for every catalog and every language. (Or if we can, test this directly in the database)

[1] http://mf-chsdi30t.bgdi.admin.ch/rest/services/ech/CatalogServer?lang=fr
[2] http://mf-chsdi30t.bgdi.admin.ch/rest/services/ech/CatalogServer?lang=de

Hi!
Just a question, should we consider migrating Mapproxy as well?

Legend for layer ch.swisstopo.swissimage doesn't work. It's layer that is also a background layer

http://mf-geoadmin30t.bgdi.admin.ch/elemoine/1381154831/rest/services/swisstopo/MapServer/ch.swisstopo.swissimage/getlegend?lang=en

In http://mf-chsdi30t.bgdi.admin.ch/rest/services/ech/MapServer/layersconfig?lang=fr&callback=angular.callbacks._1

ch.swisstopo.hiks-dufour should have "resolutions" because I think that we don't have generated all the zoom levels.

Other question: If we speak of the first edition, then timestamp should be 19451231.

/rest/services/bafu/MapServer/INVALID/getlegend returns an http 500 error, should be a 404 instead.

Most (if not all) catalog categories have selectedOpen as true, resulting in the tree being open in mf-geoadmin3 per default. In RE2, the catalog started all closed.

Why is it defined like this in our service?
Can we adapt it to reflect RE2?

See discusion here: geoadmin/mf-geoadmin3#289

Certaines class dans stopo.py ont 2 registers...
Il y a donc 2 bodId possibles pour la même classe.
L'attribut bodId est laissé vide dans le modèle.
A vérifier si ça ne pose pas de problème.

Class concernées:

• class spannungsarmeGebiete
• class GridstandPk25
• class GridstandPk50
• class GridstandPk100
• class GridstandPk200
• class GridstandPk500

Unused fields: category, topic, path, depth, id.

For htmlpopup

Do we support this permalink in geoadmin3?

baseUrl?layerId=featureId

e.g. Open http://mf-geoadmin30t.bgdi.admin.ch/elemoine/rest/services/ech/MapServer/layersconfig?lang=de in a browser tab and search for "swissboundaries3d".

Our layerconfig service returns old timestamps for certain layers. The layer I verified is ch.swisstopo.pixelkarte-farbe-pk25.noscale, where the most recent timestamp is 20111231, but in chsdi2 layers.js file, we have 20130903.

This means we have newer tiles in old application. This is probably a missing configuration in our db.

I suspect other layers to have the same problems (verified pk50).

This also leads to a bug in geoadmin3, which I will describe soon.

This should be done once we're sure of the behavior we want.

Try to avoid duplicates

At the moment all the services are topic dependent.
For some layers (such as treasurehunt) there are no assiociated topics.

Therefore, it would be useful to have a topic name that englobe all the topics. (no filter applied)

this "fake" topic could be "all".

/rest/services/all/MapServer/ch.swisstopo.treasurehunt/463/htmlpopup

There are at the moment 12 models and about 190 makos to migrate.
Here is the list of the models with the corresponding number of classes (in general 1 class = 1 mako, but it's not always true) and who is going to migrate them

foa
--> vbs.py : 2 classes
--> kogis.py : 6 classes
--> ivs2b.py : 0 classes
--> dritte.py : 2 classes
--> bak.py : 2 classes
--> bafu.py : 53 classes
--> are.py : 11 active classes (+ 5 which are commented out)

alp
--> uvek.py : 34 classes
--> evd.py : 1 class
--> edi.py : 4 classes

gud
--> stopo.py : 81 classes
--> zeitrehien.py : 8 classes

MAIN CHANGES:

Models:
--> autoload: False
--> full list of needed columns
--> other: look at the already present examples (uvek.py)
Makos:
--> located in /chsdi/templates/htmlpopup
--> look at the already present examples (bln.mako). In general: values in dictionaries

WORKFLOW:

--> make a branch for each model (dev_migrate_[modelname]_models) and push it
--> make a separated commit for each migrated file
--> once a model is OK, push the branch and open a pull request

DEADLINE:

Just a suggestion, but it would be nice to have it done by Loïc's return (16.09)

Quel attribut mettre dans "displayFieldName" quand il y a plusieurs attributs dans le preview de la mako?
Exemple: treasurehunt.mako
<%def name="preview()">
% if lang =='fr':
${c['attributes']['title_fr'] or '-'}
% elif lang == 'it'
${c['attributes']['title_it'] or '-'}
% else:
${c['attributes']['tile_de'] or '-'}
% endif
</%def>

c.bbox not supported in CadastralWebMap

once this has been merged in geoadmin/mf-geoadmin3#454

Here some SQL scripts that allow us to check the content of the BOD RE3:

-- Check that all catalog topics exist in topics tables
SELECT distinct topic
FROM re3.catalog
where topic not in (select topic from re3.topics);

Could you please do the same as
https://svn.bgdi.admin.ch/viewvc/mf-chsdi?view=revision&revision=3983

in CHSDI3

Remove unneeded parameter.

Service catalog contains sublayers. They should be removed (most probably we want the aggregate layers there).

See discussion here: https://groups.google.com/forum/#!msg/re3-dev/zolXq98ljlI/GHZ2NBf8YWMJ

I know we have some restrictions according in chsdi2 for that.

I don't really which service should be restricted though.

Could list that and do it or give back to me afterwards?