Gazetteer Interface

[dbauszus-glx]

The location of the gazetteer control in the location tab should be reviewed.

Having the gazetteer closely linked with the location listview is not ideal.

It is not easily possible to add the gazetteer to mapview elements not in the default mapp application view.

It might be better to have a gazetteer plugin which open the gazetteer input in a dialog.

[cityremade]

First fix - restored search icon for inactive location tab
#1999

[jfitzpatrick17]

• Semi-related to this, we have seen users getting confused between the layer search box and location search box (thinking they were the same thing).

[dbauszus-glx]

@jfitzpatrick17 The layer search box is an optional plugin. Can you open a ticket in the plugins repo to address this.

[cityremade]

Another possible solution.
Right now gazetteer search sits in locations tab next to layers.
It could have its own space where search results could be listed instead of elusive dropdown. This is design used in google and apple maps.

[simon-leech]

I would agree with @cityremade above!
I think the searching should move to its own tab, it's such a useful feature it shouldn't be hidden in the location panel.
Moving it to its own panel would allow the user to control the parameters of the search. Such as Search using a plugin, Search using their own data (configure the filter based on selecting a layer and then a field).
We should make sure that any changes don't break existing configurations that have pre-defined datasets defined. But it should be possible for a user to build their own search using a layer and fields, we shouldn't have to configure all possible search fields for them, that's not flexible enough.

[dbauszus-glx]

@simon-leech @cityremade How would that work with locations? The gazetteer locations are added to a locations list view in the gazetteer tab and locations selected in the mapview are added to the locations listview?

[dbauszus-glx]

The idea for a plugin gazetteer would just put the gazetteer interface into a dialog.

This is pretty simple to do with a handful lines of script.

console.log('gazetteerPlugin')

mapp.plugins.gazetteer = pluginGazetteer;

async function pluginGazetteer(plugin, mapview) {

  if (!mapview) return;

  const mapButton = document.getElementById('mapButton');

  if (!mapButton) return;

  const content = mapp.utils.html.node`<div>`

  mapp.ui.Gazetteer(
    Object.assign(mapview.locale.gazetteer, {
      mapview,
      target: content,
    }),
  );

  plugin.dialog = {
    header: 'Gazetteer',
    content,
    target: document.getElementById('Map'),
    closeBtn: true,
    onClose: () => {
      plugin.btn.classList.remove('active');
    },
  };

  // Create the node for the button
  plugin.btn = mapp.utils.html.node`<button
    data-id="plugin-gazetteer"
    title="Gazetteer Dialog"
    onclick=${(e)=>{
      if (plugin.btn.classList.toggle('active')) {

        mapp.ui.elements.dialog(plugin.dialog)

      } else {

        plugin.dialog.close()
      }
    }}>
    <span class="material-symbols-outlined">search`;

  // Add button to panel
  mapButton.append(plugin.btn);
}

[cityremade]

Best matches for the search would be listed in the search tab. Then click on search result would do what the click in dropdown does now. Search results could be kept in that tab for further reference.

Also I think dropdown in a dialog is quite eeek

[jfitzpatrick17]

Having the search icon change to the location icon is confusing for the end user, the UI should main consistent / search icon shouldn't disappear.

One option we could explore is having the gazetteer search always available e.g. top right and include the layer/locations alongside the other icons in the control panel on the left hand side of the screen - with the layer panels and location selections appearing as dialogues when selected (to save screen space).