Topic external service

[davidoesch]

als Diensteanbieter WMS WMTS

will ich Datenbenen meiner Dienste in einer Verzeichnisstruktur (https://help.geo.admin.ch/?id=32&) Katalog (topic=thirdparty) darstellen können ohne die Daten in die BGDI physisch zu integrieren

weil ich einen Permalink auf einen von mir betriebenen Datensatz in map.geo.admin.ch darstellen will und somit meine einfachen WebMapping Anwendung ablösen kann. Kunde kann meine Daten im Katalog browsen.

Akzeptanz Kriterium

• [ ] Erfassung der layer in einem github basierten System (json csv, yaml, text ähnlich wie https://github.com/geoadmin/mf-geoadmin3/blob/master/src/js/ImportController.js

• [ ] Verzeichnis Struktur mitgegeben werden ( Zb +-- International +-- Schweiz | +-- Schwyz __ +-- Rollstuhlparkplätze __ +-- Leitungskataster | +-- Solothurn __ +-- Velowege

• [ ] Attribute pro layer must be consumed via external services KOGIS will define the possible config paramteres (getCap - , geocat, a yaml file, https://www.w3.org/TR/vocab-dcat/ etc)/ which will be used for

  • [ ] unique ID [link to service type, named layer, version, Url eg
    WMS endpoint(s): link wms und substruktur wird aufgebaut wie import

  • [ ] Titel nicht multilingual aus GetCap (hiking trails)

  • [ ] data owner in footer (Kanton solothurn)

• [ ] publiziert via PR / deploy mf-geoadmin

Deliverables:

• [ ] user deliveres a GetCap gemäss OGC
• [ ] uses GetLegend gemäss OGC
• [ ] uses GetFeature gemäss OGC
• [ ] Github baisert wie ImportController.js
• [ ] if wmts not avail. : greyed out: (we need test owslib in bg if 404 etc)

out of scope:

• implementation in sphinx search
• implementation attribute search

How to Demo:

• [ ] link auf Verzeichnisstruktur geschlossen zb https://map.geo.admin.ch/?catalogNodes=532,533
• [ ] link auf datensatz https://map.geo.admin.ch/?lang=en&topic=ech&catalogNodes=532,533&bgLayer=ch.swisstopo.pixelkarte-farbe&layers=WMS%7C%7CBB.farbig%7C%7Chttp:%2F%2Fgeoweb.so.ch%2Fwms%2Fgrundbuchplan%3F%7C%7CBB.farbig%7C%7C1.3.0&E=2607328.96&N=1229103.65&zoom=9

Backlog:

• [ ] source WMS endpoint: link wms und substruktur wird aufgebaut wie import + Get Cap auslesen or "WMS||BB.farbig||http://geoweb.so.ch/wms/grundbuchplan?||BB.farbig||1.3.0 "] or CSW endpoint + ID zu datensatz

  • [ ] Kurztitel Multingual (Solothurn hiking trails )
  • [ ] Abstract (hiking trails contains the hiking trails of solothurn...)
  • [ ] link to geocat ID : eg (4a064664-a346-4c1a-b424-4e8a0f0b56cb)
  • [ ] link to services ([Download, URL opendataswiss],[WMS, URL GetCap],[WMTS, URL GetCap],[LinkeData, URL GetCap]) - optional
  • [ ] link to DataStatus (YYYY.MM.DD )
  • [ ] infobox nutzt "Attribute pro layer " wie oben definiert

[davidoesch]

next step: discuss with @gjn this approach

[danduk82]

ping @rebert

[davidoesch]

Above this is an idea: we are open for suggestions

[gjn]

I'd like to discuss this first.

On Thursday, January 17, 2019, Andrea Borghi wrote:

ping @rebert

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/geoadmin/mf-geoadmin3/issues/4668#issuecomment-45516835

[danduk82]

It is worth discussing, yes.

@gjn don't worry there is MVT to put online first.

@davidoesch IMO this kind of features should be discussed when we write down more detailed specs for the RE4 viewer. I add the re4 whishlist tag

[davidoesch]

its not RE4 related: its triggered by Cantons project according to the jahresplanung

[davidoesch]

we don't do RE4 project mmgt here, this is why I removed the whishlist tag . PM is done in JIRA (corporate decision)

[danduk82]

ok

[gjn]

We'll also need a find a way to integrate those layers so they could be found via search - as well the wms/wmts in the import list. I have some ideas here.

This issue is a very nice idea trigger!

On Friday, January 18, 2019, Andrea Borghi wrote:

ok

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/geoadmin/mf-geoadmin3/issues/4668#issuecomment-45549956

[davidoesch]

discussed wit @edigonzales and @kuneppe

[gjn]

Guys, if we keep testvier on a branch, we meed to mark issues somehow to know if it's for testviewer, map.geo or (hopefully not) both.

On Thursday, January 31, 2019, David Oesch wrote:

Assigned #4668 to @gjn.

-- You are receiving this because you were assigned. Reply to this email directly or view it on GitHub: https://github.com/geoadmin/mf-geoadmin3/issues/4668#event-210895411

[davidoesch]

So proposal

• if we don't use a fork :tag re4
• branch: we use tag re4

[procrastinatio]

You may use the new config_urlto point to any (bgdi|admin).ch address holding valid layersConfig, service and topic configuration files

Dummy layer from hypothetical config

We need to fully describe the WMTS layer though. Same for 3D and vector data.

[davidoesch]

is there a primer on topic configuration to achieve the above wanted behaviour?

[procrastinatio]

The topic list is only a file with the background layers and a list of layers to display/activate. The topic configuration itself (topic image, translation, etc..) must already be present elsewhere. For now, we do not allow external resources (non (admin|bgdi).ch to be loaded from the layersConfig and there is some black magic with resource's names ((dev|int|prod).

POC: External WMs layers from config (no WMS im Url) and Menü https://mf-geoadmin3.int.bgdi.ch/mom_external_cfg/1902281659/index.html?config_url=%2F%2Fmf-geoadmin3.int.bgdi.ch%2Fconfigs%2F5555&lang=de&E=2791453.50&N=1156061.60&zoom=4&topic=ech

[davidoesch]

@edigonzales kannst du mal das beispiel inhttps://github.com/geoadmin/mf-geoadmin3/issues/4668#issuecomment-468673847 prüfen?

[edigonzales]

@davidoesch was genau prüfen?

[davidoesch]

sorry --wrong issue- this one: https://github.com/geoadmin/mf-geoadmin3/issues/4725#issuecomment-461707882

[davidoesch]

might be solved via https://github.com/procrastinatio/geoadminch_configs @boecklic @gjn your thoughts?

[davidoesch]

as discussed... rather an UI based approach to edit content than json files

[davidoesch]

after 2 years: ticket is still valid. this would ease "import " in web-mapviewer - @pakb @boecklic

[davidoesch]

will be addressed partly within https://github.com/FHNW-IVGI/Geoharvester/ keep on pushing this topic @p1d1d1 IM sure @procrastinatio @mariokeusen will suport you since this pareto of NGDI