[Google Maps API v3] Re: What constitute's the need for a "Premier License"?
Thank you both. That might indeed add a very different twist to what I read into Google's information. As long as Google viewpoint is in sync, that's great. If you will forgive me, I will again clarify the process, as this is somewhat of a fork in the road regarding whether my current (and future) development will incorporate Google maps in any way, shape or form. 1) There may or may not be a charge for the base app (yet to be decided). Most likely, there will be a base charge of a couple of bucks. 2) The user enters their place of birth, either by means of an address string that will be sent to Google for geocoding, or by means of selecting the place of birth from a map(s). There is NO charge to the user for entering this data or for subsequently obtaining the lat/lon of that location. The use of the map is free. 3) This lat/lon information, however, is then used by the app to create a "natal chart" that is typically about 20 printed pages in length. There is NO CHARGE for this chart. 4) The user has then the option of obtaining a substantially expanded chart, at a nominal fee. This version will typically be well over 100 printed pages in length. 5) Again, there is no charge for the use of the maps in either case. If I read both your definitions correctly, then I believe I am OK with the free version. Please advise. I do have other ways of obtaining lat/ lon for the paid version, if I need to. I have an internal database of lat/lon for world cities with over 300,000 records. The Google map implementation is just a bit slicker and the search is more efficient, as it seems to work better in those situations where an address has been entered in a weird way. I thank you again for your clarifications... greatly appreciated! Jack On Mar 8, 11:31 am, Michael Geary wrote: > On Tue, Mar 8, 2011 at 9:53 AM, Michael Geary wrote: > > Imagine your app worked like this: > > > 1. Look up your birthplace on a Google map for free > > 2. Pay to find out more > > > Then you could use the free API. > > Aw rats. I might have this wrong. I'm sure this use of the *map* would be > OK, but if the "pay to find out more" step involves the use of the > *geocoding results* obtained in step 1, that might be a problem for the free > API. I'm not really sure on this one. > > -Mike -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Re: What constitute's the need for a "Premier License"?
Thank you both. That might indeed add a very different twist to what I read into Google's information. As long as Google viewpoint is in sync, that's great. If you will forgive me, I will again clarify the process, as this is somewhat of a fork in the road regarding whether my current (and future) development will incorporate Google maps in any way, shape or form. 1) There may or may not be a charge for the base app (yet to be decided). Most likely, there will be a base charge of a couple of bucks. 2) The user enters their place of birth, either by means of an address string that will be sent to Google for geocoding, or by means of selecting the place of birth from a map(s). There is NO charge to the user for entering this data or for subsequently obtaining the lat/lon of that location. The use of the map is free. 3) This lat/lon information, however, is then used by the app to create a "natal chart" that is typically about 20 printed pages in length. There is NO CHARGE for this chart. 4) The user has then the option of obtaining a substantially expanded chart, at a nominal fee. This version will typically be well over 100 printed pages in length. 5) Again, there is no charge for the use of the maps in either case. If I read both your definitions correctly, then I believe I am OK with the free version. Please advise. I do have other ways of obtaining lat/ lon for the paid version, if I need to. I have an internal database of lat/lon for world cities with over 300,000 records. The Google map implementation is just a bit slicker and the search more efficient, as it seems than an address has been entered in a weird way. I thank you again for your clarifications... greatly appreciated! Jack -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] What constitute's the need for a "Premier License"?
I'm having a very difficult time determining the specific needs that make a "Premier License" a necessity. I find Google's documentation in this regard to be extremely confusing and inconsistent. The closest post I've found that addressed the same issue was placed Sep 21, 2010 and still has NO replies... http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/a82b929b0b16616a/6ed72783f1a9627d?lnk=gst&q=premier#6ed72783f1a9627d I'm developing an app that requires the lat/lon of the user's birthplace. I built a great mechanism by which the user could get the information either by doing a string search for address/city/state or by selecting the location from a map. Both methods utilized the JavaScript API V3 to return the geocoded location. This one piece of information probably represents less than 1% of the total application development, but is essential to the rest of it. THEN, I came across something in Google's API documentation that makes me think that ANY use of their APIs in a "paid" app requires a $10,000/ yr license... even it the cost of the app was only $0.99. I'm finding it very difficult to get a solid answer regarding what constitutes the need for a "Premier" license. I can't imagine that there could be such a fine line between "free" and $10,000+/yr. Am I missing something in the legalese? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Re: Alternate service for geocoding an address.
"You must have searched extensively..." Where would the world be, without good British sarcasm? The problem isn't the LACK of options, but the extremely large selection thereof. I've already wasted way too much time filtering through the numerous dead-ends. I was hoping that someone might might share their experience related to a previously encountered search to satisfy a similar need. Thanks anyway. On Mar 3, 9:17 am, Rossko wrote: > > WHAT I NEED: I'm wondering if anyone can suggest some good options > > for an alternate service for the acquisition of geospatial data (lat/ > > lon) based on the search criteria stated above. > > You must have searched extensively ; try here > -http://groups.google.com/group/google-maps-api/web/resources-non-goog... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Alternate service for geocoding an address.
I'm currently working on an iPhone/iPad application that requires the latitude and longitude of a user's birthplace. To acquire these coordinates, the user would enter a search string containing a varying combination of Address/City/ST/Country, from which would be returned one or more standardized (formatted) address and subsequent lat/lon coordinates. If there is only one returned value, the user would accept it or opt to redo the search. If there are multiple returned values, the user is given the option to select one of the values or redo the search. Once acquired, I need only the lat/lon values, though I do display a map for the purpose of confirmation. My current development incorporates the JavaScript API v3. But, while the current development is for a "free" application, I will no doubt want to launch a second version (or possibly an upgrade to a "premium version" for which I will charge a fee. (Why go to all the work of development just for the "exercise"?) And it takes way too much time to develop the interface and back-end support to just turn around and start all over for a paid version. While the acquisition of this piece of information represents less than 1% of the total work involved in the app development, it is nonetheless critical to the overall application. All the related work has already been completed, and up to now I have used my own 70,000 record zipcode database for this purpose. Unfortunately, 69,000 of the total records are US-based only and I need a more global coverage. I thought that the Google Maps approach would provide an excellent solution, as they have a very sophisticated set of routines. But reading the fine print of their user agreement, I'm not so sure I want to be so restricted with regard to my use of the application in possible (probable) future fee-based apps. WHAT I NEED: I'm wondering if anyone can suggest some good options for an alternate service for the acquisition of geospatial data (lat/ lon) based on the search criteria stated above. Thanks. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
Re: [Google Maps API v3] Is it possible to convert a "LatLng obj" to Lat/Lon coordinates?
Thank you, Mike. I had tried latlng.lat() and latlng.lng() even before seeing the table of Methods you indicated. I had also tried results[0].geometry.location.lat and results[0].geometry.location.lng without success. I've been working with navigational charts for many years and I'm one a very small list of NOAA authorized distributors for their charts. I'm not used to referring to "longitude" as "lng", but as "lon". My best guess is that I was probably using .lon() rather than .lng() out of habit. Who knows how long I'd have been playing around with this before I figured out the problem. Thanks for saving me a great deal of lost time and effort! Jack -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
[Google Maps API v3] Is it possible to convert a "LatLng obj" to Lat/Lon coordinates?
Although I've been writing code for more years than I care to admit, I am a virtual newbie to Google's Mapping API. I'm currently developing an iPhone/iPad application that uses a Google map to select the location of their birthplace. On initialization, a world map is presented along with a text box for input of city, state, country, etc... whatever is needed to identify the location. This data then uses the JavaScript API v3 to convert the data into map coordinates zooming the map to appropriately identify the results. So far, so good. The LatLng object works great for displaying the map, etc. Once the map is presented, however, I then need the actual latitude and longitude values for the application itself. It took me considerable time dealing with JS errors, before I realized that LatLng is NOT actually a string, but an object. (Yeah... I know... I should have read closer.) I have done considerable searching, but can find no solution for converting the "object" into a "string", so I can use the values in my application. While the LatLng object works quite well for Google's own maps, it certainly diminishes it's usefulness for anything else. I can't imagine that I'm the only one facing this dilemma, but I neither can I find a published solution. Any assistance would be greatly appreciated. Thanks, Jack -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
