When scrolling, the platform map widget is occasionally misplaced. When platform widgets are not included in a scroll view, it works beautifully. This clever approach to layering make them appear the same as other Flutter widgets. This means that the map widget must scroll along with other content.įlutter positions native platform widgets ( platform views) over top of the Flutter view hierarchy. With mobile devices having smaller screens, scrolling is a necessity. My app presents a map with weather data and various charts. There were two issues that prevented me from using Google maps in my app: 1. This post details the issues that I encountered and how I ended up solving the problem by creaing a plug-in vector_map_tiles to add support for vector tiles to flutter_map. The platform/Flutter combination is not perfect, and for my use-case isn’t good enough for a prodution app. The resulting map looks and behaves beautifully, except when it doesn’t. Maps are commonly added using the google_maps_flutter package, which uses native platform widgets to embed a Google map in your Flutter app.

If it does, just double-check the combination of the ' Geolocation' and 'Coordinates' settings for possible errors.Flutter is a huge productivity booster except for a few sharp edges, one of which is embedding maps. It should look like this:Īt this point, you should be able to handle the 'can't warp' error in most of the cases that it might happen to you. If the set geolocation values are incorrect in the chosen coordinate system, you will not be able to preview the footprint of the image (the 'VIEW FOOTPRINT' button at the bottom of the window will be disabled). You actually don't have to go through the whole wizard to learn that you made one of the mistakes mentioned above. If you set any of the geolocation latitude values beyond this range, you'll most probably encounter the error.Ĭhange the geolocation settings (using the 'Geolocation' menu) to be inside the bounds defined by the chosen coordinate system. For example, the Web Mercator projection is defined between 85.06°S and 85.06°N.

Georeference the image once again using the visual georeferencing tool ( 'Geolocation' -> 'Assign visually.')Īnother common cause for the 'can't warp' error is setting the input image geolocation values out of the bounds of the chosen coordinate system.

Choose the input coordinate system you wish to use using the 'Coordinates' menu.

Change the setting in the 'Geolocation' menu to the default one (or any other than 'GCPs' for that matter).

Therefore, if you chose the GCPs in the Mercator projection, and then switched to WGS84, the GCPs you picked will not make any sense in the new projection. Take for example Web Mercator(EPSG:3857) and WGS84(EPSG:4326) - the former uses meters as the basic unit while the latter operates on degrees and both have completely different bounds. The reason for it is that the GCPs are saved in the coordinate system that was chosen at the moment of opening the georeferencing tool and some coordinate systems are inherently incompatible. If you changed the input coordinate system after georeferencing the image, you might get the 'can't warp' error.

If you used the 'Assign visually' function from the 'Geolocation' menu, you had to choose the ground control points (GCPs), to overlay your input image over the basemap. It might happen that, while trying to render a map, you'll get the error that looks like this:īelow, you'll find the two most common causes for this error and solutions to fix them. In this article, we'll explain the possible reasons for such an error and show you what you can do to fix them. In some cases, while working with MapTiler Engine, you might come across the ' can't warp' error message.

Maptiler render failed