by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Sami Mäkinen
    @ZakarFin
    Right, I had an ä in the address :)
    Can't make it to #geobeers today but keeps us posted about the location @SannaJokela :)
    Jussi Arpalahti
    @jussiarpalahti
    Can’t seem to find this geobeers thing from the internets :scream_cat:
    Sami Mäkinen
    @ZakarFin
    I think devAlpo is today. Usually theres geobeers at the end
    Jussi Arpalahti
    @jussiarpalahti
    Oh, that HRI/OKF thing at Maria. There’s a party at Thursday too :grin:
    Sami Mäkinen
    @ZakarFin
    Is it possible to have the next PSC meeting on monday 11.11 instead of tuesday 12.11? Looks like I'm fully booked for tuesday
    Jussi Arpalahti
    @jussiarpalahti
    Works for me.
    Timo Sallinen
    @tsallinen
    OK for me also.
    Sanna Jokela
    @SannaJokela
    Ok for me
    Sami Mäkinen
    @ZakarFin
    :+1:
    Marko Kuosmanen
    @kuosman
    Ok for me also
    Sanna Jokela
    @SannaJokela
    I can update the calendar
    Sami Mäkinen
    @ZakarFin
    Thanks!
    Sanna Jokela
    @SannaJokela
    PSC meeting today, I thought that would it be ok, if we discussed some acute Oskari maters instead of normal "news". E.g. 3D, OGC API or the idea for Oskari UI development?
    Sami Mäkinen
    @ZakarFin
    Sure, any topic is up for discussion
    Sanna Jokela
    @SannaJokela
    What is the most acute? :)
    Sami Mäkinen
    @ZakarFin
    Well the next Oskari version includes the new optional/parallel implementation mapmodule for olcesium. Ogc api features has been supported for a couple of releases now. Not sure about the latest situation with the ui refresh :)
    Choose your poison
    Sami Mäkinen
    @ZakarFin
    The removal of tranport will probably not make it to the upcoming release
    But things might not work perfectly with 1.54 and transport :)
    By that I mean no-one has tested it since all our environments have been migrated from transport to the new system
    tmiosmauli
    @tmiosmauli
    IMHO you could discuss 3D and esp. needs in different organizations in terms of the third dimension
    "what would you like to do with 3D?" :)
    Sami Mäkinen
    @ZakarFin
    My interest would be to know if anyone has tested the new WFS-backend
    tmiosmauli
    @tmiosmauli
    +1 for that!
    Sanna Jokela
    @SannaJokela
    ok, let's do that :)
    Sanna Jokela
    @SannaJokela
    just a sec, network problems
    Sami Mäkinen
    @ZakarFin
    seems I cant join to meeting
    it says "still trying to connect"
    Sanna Jokela
    @SannaJokela
    try now
    Sanna Jokela
    @SannaJokela
    Hello! PSC meeting today, add your OIPS and issues to the memo, please! https://docs.google.com/document/d/1Je1XCj73ga33TN6OPZDb-qRRteIGsB0AT4mjvfK9Vg8/edit#
    Sami Mäkinen
    @ZakarFin
    @SannaJokela will you be doing the PR for the notes still?
    Sanna Jokela
    @SannaJokela
    @ZakarFin yes for now, but I have been a bit busy since the meeting, I'll try to add the memo to github on friday
    Sami Mäkinen
    @ZakarFin
    Great great, just checking since we talked about you not having to do anything anymore :P
    Sami Mäkinen
    @ZakarFin
    A friendly reminder we do NOT have a meeting today but if there are things you would like to bring to our attention please do so whenever you can :)
    Sami Mäkinen
    @ZakarFin

    Hi guys, here's some plans on reorganizing the database regarding wfslayers:

    I'm working on removing transport related server code and I'm suggesting that all relevant info in portti_wfs_layer table is moved to oskari_maplayer.attributes.

    Currently:

    portti_wfs_layer.selected_feature_params (these are lists of feature data to show to the user)

    {
        "default": ["kunta_fi", ...]
        "fi": ["kunta_fi", ... ],
        "sv": ["kunta_se", ...]
    }

    portti_wfs_layer.feature_params_locales (localization for said data NOTE! They need to be in sync with the arrays in selected_feature_params):

    { 
      "fi": ["Kunta","Ruutu-ID","ID-nro","X-koordinaatti","Y-koordinaatti","Väestö","Miehet","Naiset","Ikä 0-14","Ikä 15-64","Ikä 65+"],
      "sv": ["Kommun","Rut-ID","ID-nr","X-koordinat","Y-koordinat","Folkmängd","Män","Kvinnor","Ålder 0-14","Ålder 15-64","Ålder 65+"],
      "en": ["Municipality","Grid ID","ID No.","X-coordinate","Y-coordinate","Population","Male","Female","Age 0-14","Age 15-64","Age 65+"]
    }

    My thought is to combine these in oskari_maplayer.attributes:

    {
        data: {
            // portti_wfs_layer.selected_feature_params (defaults to geoportal default language when requested):
            selected: {
                fi: ["kunta_fi", ...],
                en: ["kunta_en", ...]
            },
            // portti_wfs_layer.feature_params_locales (changing the model so these are not tied to selected data. These will be used to switch the UI name IF said feature data attribute should be shown to user):
            locale: {
                fi: {
                    "kunta_fi": "Kunta",
                    ...
                },
                en: {
                    "kunta_en": "Municipality",
                    ...
                }
            }
        },
        // portti_wfs_layer.feature_namespace_url (Looks like this is the only required data from portti_wfs_layer in addition to the 2 above)
        namespaceURL: 'http://jotain'
        ...
    }

    Looks like
    oskari_maplayer.name == portti_wfs_layer.feature_namespace + portti_wfs_layer.feature_element already

    And these tables can be removed since we don't support SLD or digging/normalizing data from complex features currently on the server side:

    • portti_wfs_template_model
    • portti_wfs_layers_styles
    • portti_wfs_layer_style
    • oskari_wfs_parser_config

    Any thoughts on this?

    Marko Kuosmanen
    @kuosman
    Looks good and simplifies database structure. Regarding WFS layer(s): is there support custom sld's now already in new wfs ? One customer case is that at ~10 wfs layers (old wfs motor, not updated yet to new) has defined custom sld style in database.
    Sami Mäkinen
    @ZakarFin
    unfortunately no
    There's no support for SLDs
    not even planned
    Do they need it as WFS though?
    Maybe use SLDs on Geoserver and publish them as WMS?
    Sami Mäkinen
    @ZakarFin
    fyi, Started doing the WFS-changes in oskariorg/oskari-server#509
    tmiosmauli
    @tmiosmauli
    Don't want to interfere with the PSC's discussions too much, but GeoServer has the ability to use external WFS's, see: https://docs.geoserver.org/latest/en/user/data/cascaded/wfs.html
    In their own words "GeoServer has the ability to load data from a remote Web Feature Server (WFS). This is useful if the remote WFS lacks certain functionality that GeoServer contains."
    So Sami's suggestion might be rather straight forward to implement, not sure about performance. It sounds like a legacy solution so maybe the performance isn't so great to begin with..
    Marko Kuosmanen
    @kuosman
    Ok, I add these instructions to task when upgrading Oskari :)
    Customer has WFS layers an dthey edited them by content-editor... maybe default users can see these layers as WMS
    Sami Mäkinen
    @ZakarFin
    Sure, that could be an option