How to set the display boundary

[SanSanNiang]

How to set the display boundary ?
Only the set area is displayed, and beyond the boundary can not be dragged

[JaffaKetchup]

@SanSanNiang Hi there,
Sorry, I don't quite understand your request? Can you explain more information. Many thanks.

[SanSanNiang]

@SanSanNiang Hi there, Sorry, I don't quite understand your request? Can you explain more information. Many thanks.

I tested a map, based on Epsg3857,which displays part of the map.
Now, the map shows the exceeding part, and the exceeding part is gray. What should I do not display the exceeding part?

[JaffaKetchup]

Ok, related to #1103 perhaps?

[JaffaKetchup]

I can't help fully, as I've never dealt with it before, but you should be able to set bounds in MapOptions? Please try that or look at the issue linked above, and let me know if it works.

[SanSanNiang]

I can't help fully, as I've never dealt with it before, but you should be able to set bounds in MapOptions? Please try that or look at the issue linked above, and let me know if it works.

With the sw and ne coordinates of the map as the boundary, although there are restrictions on dragging, there are still excess parts displayed.

[sam-parks]

I'm also experiencing this issue:

[JaffaKetchup]

@sam-parks Can you say which version/commit this problem appeared in, or have you just started using it?

[JaffaKetchup]

Can you both please write a minimal reproducible example for me to test and experiment with? Many thanks.

[sam-parks]

@JaffaKetchup

I did just start using the package so its version 0.14.0

FlutterMap(
                options: MapOptions(
                  zoom: 2,
                  maxZoom: 7,
                  minZoom: 2,
                  center: LatLng(15.96, 45.81),
                ),
                children: <Widget>[
                  TileLayerWidget(
                    options: TileLayerOptions(
                      urlTemplate:
                          'https://api.maptiler.com/maps/bright/{z}/{x}/{y}.png?key=FHzUbZwstZKBiAQE7D4V',
                    ),
                  ),

[SanSanNiang]

Can you both please write a minimal reproducible example for me to test and experiment with? Many thanks.

the package version：0.11.0
FlutterMap(
mapController: this._mapController,
options: MapOptions(
center: LatLng(39.813363,124.143537),
interactiveFlags: InteractiveFlag.all &
~InteractiveFlag.rotate, // Disable map rotation
slideOnBoundaries: true,
swPanBoundary:LatLng(39.743098,124.093323),
nePanBoundary: LatLng(39.861238,124.197371),
minZoom: 12.0,
maxZoom: 14.0,
zoom: 13,

                      ),
                      layers: [
                        TileLayerOptions(
                          maxZoom: 14.0,
                          wmsOptions: WMSTileLayerOptions(
                              baseUrl:
                                  'http://124.93.251.50:8085/geoserver/dandongport/wms?',
                              layers: ['dandongport:dandongport_tile'],
                              version: '1.1.1',
                              ),
                        ),
                      
                      ],
                    ),

[JaffaKetchup]

Please update to the latest version 0.14.0 if you can. If not use advanced installation to use the latest commits from this package on branch 'master'. Support is limited for older versions, due to high maintenance pressures at the moment.

@sam-parks I'm not familiar with these options, but the bounds and boundsOptions parameters (in MapOptions()) might work better for you? Please try and get back to me.

[sam-parks]

@JaffaKetchup I tried messing around with bounds and boundsOptions but that only seems to change the bounds of the initial position. I can still scroll to the grey areas.

[JaffaKetchup]

In that case I will need to investigate further. Many thanks for your help!

[stx]

Same issue here using Mapbox tiles (not sure it matters though.)

Setting panBoundaries doesn't seem to affect it - at least vertically.

[stx]

For @JaffaKetchup or whoever else is interested, I created a $100 bounty for a nice and timely fix for this for mobile and web. Source

[stx]

This looks fixed by PR #1211 and I think we can close it now for the bounty. Thank you @ibrierley!