Hi All, There are a number of attempts to use google maps in iphone applications. I've tried this using the current JavaScript API but the JS interpreter available in the iphone SDK is too slow, the main.js is just too big, the tiles the JS API loads are too big, plus the javascript object allocations are limited to 10MB so the map stops working after a while. (theres a reason why apple doesn't use the JS API in their native map)
For the above reasons there are a number of open source efforts underway to implement a native iphone map solution using direct tile access using google/microsoft/yahoo tiles. For obvious reasons most people want googles tiles. Does this violate the current TOS/TOU and if it does will the new TOS/TOU allow this. We developers aren’t looking to violate any terms we just want to create apps that work well. Accessing the tiles directly allows independent developers to create an app with nice smooth iphone panning/zooming very similar to the native iphone map app. I'm pretty sure the Andriod mobile platform map API is just a wrapper for direct tile access, so if this is the case I would assume we should be able to use a similar approach on the apple platform for apps that are free and without subscription. Pamela you seem to be the only one who answers these types of questions from a google point of view. Can you please give me your opinion on this and the roadmap ahead or someone in google I can contact for more information. thanks, Matt On Oct 10, 5:53 pm, Lance Dyas <[EMAIL PROTECTED]> wrote: > Yes, and this reminds me of why some of the GIS industry (I am a > software engineer for MicroImages ... creators of TNTmips) are actually > inclined to embrace Google Maps. They are a > great "presentational media" especially for interfacing with the average > joe and it gives > a prod to the industry to improve our GUI, TNTmips our main GIS > software now has the drag > the map style panning and an overview map built in to the window and I > blame it on Google, > These tools are like the irfan view great gadget but it doesnt "really" > step on the toes of photoshop why would it. > > Simon wrote: > > Thanks Andrew, > > > There are far easier and more direct ways of providing instruction to > > remote systems than through Google Maps API. The API is fantastically > > useful, primarily as a visualisation and information dissemination > > tool but not for systems control. We do not intend to enter the domain > > of hard real time systems, and sensors recording pollutant levels or > > environmental conditions are generally discreet and single function in > > terms of the phenomena they observe. > > > Thanks, > > Simon > > > On Oct 11, 12:10 am, Lance Dyas <[EMAIL PROTECTED]> wrote: > > >> Simon wrote: > > >> Thanks Andrew, > > >>> ... > >>> The proposed application has nothing to do with the vehicle itself -- > >>> it's all about the environment surrounding the vehicle -- therefore > >>> the display of this real time environmental data is within theTOU. > >>> All this data could be collected from a huge network of stationary > >>> sensors like weather stations but that's not cost-effective. > > >> Well I agree mostly... but only if indeed it doesnt have to do with > >> controlling the vehicle > >> ie if you are not controlling the vehicle itself via the google maps data > > > . --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
