Polygon in map search is visible

[vjrj]

When selecting the records in some area, the polygon is visible:

https://biocache.ala.org.au/occurrences/search?q=taxa%3A%22acacia%22&qualityProfile=ALA&qc=-_nest_parent_%3A*&wkt=MULTIPOLYGON(((103.55712890625+-4.610646932717078,103.55712890625%20-46.287172931144475,159.98291015625%20-46.287172931144475,159.98291015625%20-4.610646932717078,103.55712890625%20-4.610646932717078)))#tab_mapView

The same search in spatial does not:

https://spatial.ala.org.au/?q=taxa:%22acacia%22&qualityProfile=ALA&qc=-_nest_parent_:*&wkt=MULTIPOLYGON(((103.55712890625%20-4.610646932717078,103.55712890625%20-46.287172931144475,159.98291015625%20-46.287172931144475,159.98291015625%20-4.610646932717078,103.55712890625%20-4.610646932717078)))

Is this something expected or patches are welcome?

[adam-collins]

Intentional.

The hub and spatial portal serve different purposes:

• The hub is for drilling down into occurrences. It is useful to see each of the successive filters applied. I this case, the supplied WKT is an applied filter. Other text based filters are communicated with some text. For WKT this is communicated with a polygon visible on the map. Without this WKT on the map, the contents of the WKT filter applied is not communicated to the user. The communication of details about filters serves to provide accessible context as to the search results, and implies the implication of removing each noted filter during a drill up.
• The spatial portal is for mapping multiple occurrence layers, each with their own filters that may or may not include WKT. It supports the addition of occurrence layers through several drill down mechanism. It has no drill up. It does not provide an easy way to get the list of the filters applied for each layer (maybe it should do this better). When working within the spatial portal and applying a WKT to an occurrence layer, the WKT filtering process (in the what, where, when) will create an object that is optionally mapped. In the case where an externally defined WKT is used (e.g. in a link from hubs) this spatial object is not created and it should not be created. If it is required it can be exported from the source (e.g. hubs) and imported into spatial portal as a new area.

A PR that adds optional config to disable the inclusion of the WKT on the hubs map is welcome.