Whether the maps: schema is supported yet in a specific device/browser combination is nothing you nor I can do anything about directly unfortunately...

The interaction between the web browser on a device and and the start-up of an alternative app is a matter for the installed browser software and...

I've been able to reproduce the issue using the standard map with value heatmap example, especially if the data set is left un-truncated. My feeling...

The following code works for me - it uses a proper jQuery function to parse the data and makes sequential calls to map.listeners.ready to firstly...

There is a method available map._map.maxStorableZoom(map.box) - though the details of the method are currently hidden. A similar request to this has...

You are calling the right method, but just at the wrong time. If the box is set before the map has completely initialized, the zoom level will be...

Fundamentally there are two ways to create an MH5 Application. The nokia.mh5.app.embed method as described in the configuration section of the User...

For Map specific parsing of generic XML you could look at the following example. The Java ME API also offers full KML support, so if you can convert...

You will have to add a custom component or at least inject a DIV element into the DOM and move and style it yourself. The code to create a similar...

The fix for this bug has now been released on the public server.

Two of these questions are easy to answer: Read the configuration section to find out how to remove the search box - just, set the value to null....

Well the standard CSV split function is shorter: // Standard Library for spliting up Comma Delimited Texts. String.prototype.splitCSV =...

Yes it is possible but you'll need to add a fair bit of code to get it to work since there is no KML parser embedded within the MH5 framework . The...

This is down to the way that clustering algorithms work - it is a consequence of the change in the view port in each of your examples. In order to...

This error is to do with the way that the browser interprets asynchronous JavaScript - older versions of Internet Explorer are notorious for this....