Just curious why you want to do this?

I don't think you can prevent zooming/panning from happening altogether with any built-in methods, but you can at least hide the zoom controls:  Zoom Controls

Muthu,

You can set the lat/longs as filters, essentially creating a bounding box.

Here's the sort of thing you can pull off using this technique:

Best Regards,

Allan

The short answer is no. You can 'Hide the Zoom Controls', but the double-click zoom-in and the double-click-shift zoom out work without the controls showing so your users will still be able to zoom in and out without controls. There is an Idea out there asking for this feature request. It's several years old so it's probably either on the road map or has been decided against, but it still might be worth a vote.

--Shawn

It really depends Shawn, whether you want to control the background map or whether you want to control your foreground analysis.

It's entirely possible not to use a background map at all, and shove everything into the foreground, which is what you are seeing above: i.e. no background map and just filter the data for the "level of zoom", i.e. the lat/longs and the data you want to visualize.

Here we go again. Mathu ask a simple (beginner?) question:

"Can we lock the zoom level for tableau map??"

I don't consider a WMS server map to be a Tableau map. It's a different animal altogether, and certainly a more advanced level of Tableau understanding than his question implies.

Just sayin'....

--Shawn

Shawn,

You didn't read my post.  That image isn't using a map.  It's all just polygons and lines.

Allan

Are we reading the same post? Where did you say that's just polygons and lines?

--Shawn

PS: Did you forget to post a link to a blog or something?

+1 I don't see it either.

OK, I can now see how you might have thought you implied this wasn't a map (sort of hard to believe that it isn't a map). And I can also now see how this could be a solution for him. A bit of a painful solution, unless he's already familiar with QGIS or some other mapping software. And you might actually be right that his need to suppress zooming is worth taking the long way around. So I have to admit that my calling you out for posting a complex, complicated solution was premature.

Sorry about that Alan.

Cheers,

--Shawn

No worries Shawn.

I didn't explain myself fully, which is a failing of mine.

When I talk about "background maps" I'm referring to stuff like UM, or WMS, or Mapbox, or whatever.

When I'm talking about foreground analysis I'm talking about a Tableau mark type.

What you are seeing there is a large PostGIS table populated with Tableau Ready mark type formats:

OSM Land Polys,

OSM Ocean Polys,

IMPOSM Metro Extracts (waterareas) Polys and (waterways) Lines

NYC "Lion" Lines

NYC DOITT Building footprint polys

NYC MTA Subway GTFS Lines

All merged and re-projected to EPSG:4326: filtered on lat/long.  Dual-axis, mark type 1 is poly, mark type 2 is line.  The "trick" is path order, as Joe Mako famously said, Tableau (foreground analysis) mapping is just a scatterplot.

This has a couple of advantages.  I don't need to connect to a background map (for example, the Server DBA doesn't allow the ports open to UM), I can style how I want, and control the zoom.

However: that all said, it is a VERY inefficient method.  All of the above layers should just be layer groups as SHP files, with the foreground analysis being performed at run-time.  That's next, because I need to join over to some more lovely opendata.

It's just when someone says "nope, can't be done": I've found with Tableau, almost anything is possible, and there is usually a solution.

Best Regards,

Allan

Shawn Wallwork wrote:

 

 

I don't consider a WMS server map to be a Tableau map.

 

Just sayin'....

--Shawn

100% WMS.  100% Open Source.  Background map layers using Ubuntu/Geoserver/AtlasStyler.

What no voice over?

Nicely done Allan.

Cheers,

--Shawn

Do people want to hear my dulcet Scottish tones?

Best Regards,

Allan