Default Map View

Hi ​@rebecca.flack,

The default map view in the new experience cannot be disabled. The goal of this data consumption tool (“explore data”) is to allow users to explore raw data through different views, such as table view, map view, and others.

If you’re looking for a more enriched or editorialized experience, you can build:

• a no-code custom view (the main call to action would then be “Show views”)
• a code-editor asset used as a visualization, by adding a custom link.

You can then choose the most relevant option as the primary call to action.

For example, in the case below, the asset includes both a custom view and an advanced code-editor visualization within the CTA.

https://datasource.kapsarc.org/explore/assets/natural-gas-exports-by-exit-point-regasification-terminals/

​@Benwa  Feel free to add any planned evolution on this point :)

Thank you very much for the reply.

The default map view is very basic and not all that useful on some datasets. We have added a custom link which will provide easy access to the visualisation (map) but when a user sees a ‘map’ tab - that will be their first point of call (especially users of the old UI).

We have lost the flexibility to make this decision.  If this could be put forward please as a development suggestion that would be appreciated.   Many thanks!

Hi ​@rebecca.flack 

Thanks for the detailed follow-up, this is genuinely useful signal.

To add a bit of context on the intent behind this: one of the core goals of the new marketplace experience is to give each consumption tool a clear purpose and a target audience. In the old Opendatasoft portal, everything happened inside a single tool — and as a result, it was nearly impossible to understand what users were actually doing: were they filtering raw data? Consuming the API? Building a chart? All of that was invisible.

The new experience separates these intentions deliberately:

• Explore is for broad data exploration — raw data, map (when geographic shapes are present), charts
• API tool is aimed at developers who want to manipulate the data programmatically
• Custom views are curated visualizations prepared by the data publisher — a map, a dashboard, a specific perspective

This separation is what allows us to actually measure data consumption per intent, and ultimately to give data publishers meaningful insights into the ROI of their assets.

On the map tab specifically: in the new Explore (currently in beta), the map — along with raw and aggregated data exploration — is coming very soon. The goal is to consolidate everything into a single, more powerful exploration tool.

In the meantime, if a map is a key part of how your users should interact with a dataset, two options are available to give it the prominence it deserves: a dedicated custom view prepared by the publisher, or potentially a standalone asset in the catalog that links back to the dataset.

That said, your underlying concern — publishers losing the ability to control what's visible and what's front-and-center — is valid and noted. We're working on giving more control over default asset settings. Posting this in our Ideas section would help us gauge broader demand.

Benwa

Hi, ​@danny.oneill 

I think this post might give you some more explanation on the default map view.

Yier