Google maps maptiler how to#
Google maps maptiler pro#

In this case, you most likely haven't saved your Google Maps API key correctly in the settings and it's probably still empty.

It may happen that instead of getting the preview you get this message box. 'This page can't load Google Maps correctly.' You'll see the same preview by opening the googlemaps.html in your're browser.ġ. By opening the index.html in your browser and navigating to Google Maps API -> Preview, you'll see your rendering output placed over the Google map. In the output folder, you can see files index.html and googlemaps.html (except for others). Render your project using the 'Folder with tiles' option for the output format On the General tab of the Global Settings dialog (File->Settings), paste your key in the Google Maps API key field and click save.Ģ. Make sure your API key is saved in the application settings When you use 'Folder with tiles' for the output, the preview is generated for you automatically. One of the possibilities of presenting your data rendered in MapTiler Desktop is using the Google Map as the basemap for your output. Using Google Maps with API key in MapTiler Desktop Once you have your project set up, you can create your API key following these steps. You must have at least one API key associated with your project.

Google maps maptiler how to#

You can read how to set it up in the Google guide. To work with Google Maps JavaScript API, you need a project with a billing account.

Any API calls without providing a proper key are considered unauthorized and restricted. It comes in form of an alphanumeric string associating your account with your project and a specific API or SDK. It is used to secure Google Maps products from unauthorized use. It is a unique identifier that authenticates requests associated with your project for usage and billing purposes. The Google Maps API key basically works as your credentials when working with Google Maps API. We'll also take a look at how to solve the most common troubles you may possibly run to.

Google maps maptiler pro#

MapTiler Pro is a powerful tool, but the user must know what he does.īased on your feedback - we have decided to implement for a future version of the MapTiler software an estimated final output size - and warn the user in the graphical user interface if he chooses options which are probably unwanted.This article will show you where to get your Google Maps API key and how to use it within your MapTiler Desktop project. Please, before you publicly rant on the performance of a software - double check you know what you do. Your original email to our support did not contain any technical data at all (not even the data you write here on the stackoverflow). Thanks for providing the report (with ) to us. If you are interested in the math behind the map tiles, check: MapTiler automatically provides you with a Google Maps V3 viewer, which is doing the client-side over zooming out of the box. The user can always zoom deeper - but the upper tiles can be displayed on the client side - so you don't really need to generate and save all these images at all.

Deeper zoom levels do not add any visual advantage. For standard input data (aerial photo) the native suggested maxzoom +1 or +2 is the max which really makes sense. If your data are coverage maps or similar dataset it makes sense to render it maybe down to zoom level 12 or similar, definitely not deeper than 14. The software has suggested you the default maxzoom 6. It sounds like a nonsense to render the very low-res image (2600 x 2000 pixel) covering a large area (such as the South Africa) down to zoom level 21! 10 billion of map tiles at zoom level 21) by the options you have set in the software. You are trying to generate from your input 21 MBytes file about 350 GBytes of tiles (approx.