Loading...
Answers
MenuLicensing points of interest database vs. creating your own when creating a mobile app MVP?
We are considering retrieving Google Places API data and storing it in our database vs. using a licensed database (such as Infogroup).
What would be the preferred choice?
Answers
Using Google Places API and storing the results in your own database likely violates the terms of service. Likewise, you are limited to the number of calls per day to the API. If you expect users to appreciate (and pay for) the software you are generating, you should do likewise. Go with the licenced database.
According to the Google Places API license agreement you can only "store" or cache data for a maximum of 30 days and there are additional restrictions around the use of that data (see excerpt below). I think a better explanation of how long the data is going to need to be stored and how it is going to be used needs to be offered in order to determine if Google Places API is even a viable option.
Disclaimer: Please note any discussion around licensing requires both legal and technical expertise. I am not an attorney and can only offer my technical advice. The advice given in this answer is NOT legal advice. You should also consult your attorney about the legal ramifications surrounding this question.
Excerpt taken from ( https://developers.google.com/maps/terms ) on 20-May-2015
"10.1.3 Restrictions against Copying or Data Export.
(a) No Unauthorized Copying, Modification, Creation of Derivative Works, or Display of the Content. You must not copy, translate, modify, or create a derivative work (including creating or contributing to a database) of, or publicly display any Content or any part thereof except as explicitly permitted under these Terms. For example, the following are prohibited: (i) creating server-side modification of map tiles; (ii) stitching multiple static map images together to display a map that is larger than permitted in the Maps APIs Documentation; (iii) creating mailing lists or telemarketing lists based on the Content; or (iv) exporting, writing, or saving the Content to a third party's location-based platform or service.
(b) No Pre-Fetching, Caching, or Storage of Content. You must not pre-fetch, cache, or store any Content, except that you may store: (i) limited amounts of Content for the purpose of improving the performance of your Maps API Implementation if you do so temporarily (and in no event for more than 30 calendar days), securely, and in a manner that does not permit use of the Content outside of the Service; and (ii) any content identifier or key that the Maps APIs Documentation specifically permits you to store. For example, you must not use the Content to create an independent database of "places" or other local listings information."
Depends on your use case but storing API data like this is probably not best. Especially if the info may be updated frequently or if your use case is larger than a specific city/state.
Related Questions
-
What is a good starter database software for a small business?
Linux + MariaDB (Fast MySQL). Enterprise level throughput + scalability. Cost == $0. Well, cost included with whatever hosting you're using. I run a private hosting company. Some of my machines are running 250,000+ uniques/hour + have been for months. MariaDB can handle whatever load you throw at it... Well... so long as your coders know how to write high speed code. Most coders are clueless about this. Tip: Pay for expensive developers up front + you'll save huge amounts of money avoiding rewrites.DF
-
What is the pricing of bundled residential real estate data for USA, California (transactions, date of sale, price of sale, MLS pictures)
In my experience, this data has been at no cost. Most property appraiser sites offer sales data as an excel file for download. Each property can be looked at with exterior photos, or base floor plans. It would take quite alot of dara entry to input into a program, the issue would be the accuracy, if properties change hands within a year. Hope this helps! Warm Regards, MargieMK
-
How can I create a database of emails for a specific client market?
Have you thought about suggesting existing Customer Relationship Management (CRM) platforms? While they all have learning curves to tackle, they will still surely be time savers compared to starting from scratch. I'm a big fan of Infusionsoft and a Certified Partner but if a robust solution like that is too big for your needs then there are others like Hubspot CRM or even Insightly. They each manage contacts like a boss however they will each also have certain pros and cons that you'll want to research for your specific needs as well.JF
-
Is there demand for a service that sells database of contact information of varied sectors and geographies? If so, how do I market this product?
There are a lot of players in this market. Many that integrate with all the major CRMs and append and clean data. I would say I get at least 1 email a day from a data vendor and I have been on countless demos and calls and because my client is so niche they never have more 5-10 records even viable for me. I am sure for larger companies with broader markets this works well. They all tend to have very aggressive sales outreach. I have one company that has called me every 3 months for the past 2 years. At this point hes basically just asking about my health and the weather :)NP
-
What is the easiest way to store log-in and customer information obtained from our company website?
Well you should store it in a database, most probably an SQL based database. MySQL is a fine start, free and easy to set up. But, you had best start thinking about security issues, especially if you are planning on storing credit card and other personal information. Hackers go right through the standard fare and many companies do nothing to encrypt their data at all, which in some countries is a criminal offense. Best hire a professional to look at your system setup and see what can be done.SK
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.