Integrate vector querying for vector layers

[simboss]

Currently there is no support for querying vector layers in the MapStore product although we have widgets for doing all the bits.

Likewise MapStore 1 we need to be able to to query vector layers via WFS when available.

TASKS:

• Remove useless code from existing codebase
• Enable drawing on map for spatial filter
• Enable tool only for WMS vector layers (get the info from the map configuration, either saved from catalog or not)
• Complete results panel: see related issue Complete the results panel #1320

[offtherailz]

Maybe I created this story that seems to be duplicated. #1121

Should I close it and port the discussion and proposal here?

[mbarto]

I would say yes.

Il 11/ott/2016 12:40, "Lorenzo Natali" notifications@github.com ha
scritto:

Maybe I created this story that seems to be duplicated. #1121
#1121

Should I close it and port the discussion here?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1104 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpGYJakNviAfU2Mum_Fp23v8eQhOA1Sks5qy2eLgaJpZM4KSUW7
.

[offtherailz]

Porting the duplicated US details here :

We should so integrate the current query panel and the feature grid to create an advanced search tool for the layers that covers the functinalities available in the old QueryPanel + FeatureManager + FeatureGrid available in MapStore (1).

Estimated tasks and decisions:

• Provide a way to select the layer to query (e.g. a button in the TOC, context-menu). This should open the panel. This should be a panel like the toc (maybe from the opposite side) or inside it.
• Add support to retrieve attributes and types from DescribeLayer ( current tool is configured statically).
• Support numeric attribute validation
• The search action should switch the same panel to the table of results, and provide a button to back to search.

Advanced features:

• retrieve existing values from WPS, with pagination (requires changes in the widget library used, see react-select and react-select-virtualized

[Gnafu]

Here is a mockup of how it will look like:

[mbarto]

Let's put pagination into account...

[simboss]

We are missing the export of features as well as the ability to zoom to a single row on the map.
We need to have the same functionalities that we had on MapStore 1, the layour can be completely different though.

[Gnafu]

The following is designed for desktop users (mobile will have a separate user story), it has:

• Button to zoom to single feature
• Column sorting
• Pagination (should we also consider the infinite loading?)
• Highlight results on map
• Export (the server should be queried for supported formats)
  • "Current page export" and "All pages export" options should also be available/configurable

[simboss]

+1 on infinite loading, although I would expect something that allows me to jump to end and when I reach the end to jump to front.

Not sure this is feasible according to all WFS versions and paging. The same applies for the # of pages you are showing there.

[Gnafu]

Real pagination can be done only if the server supports it:

• it responds with the "totalFeatures"
• it supports "startIndex" and "count" parameters

It the server doesn't, the pagination will be "fake", loading a reasonable amount of results and browsing them without server interaction. ("reasonable" to be defined)