Suitable for all organisations that are required to collate, store and generate borehole site logs in a timely and orderly fashion. Can also be used for the storage of .ags data if setup correctly. Handles multiple projects well but is not without hiccups when used regularly. I believe it is possible to draw section views however have not done so myself.
It is most suited for someone who has a physical office, particularly a retail store which helps them to promote the business locally. I would suggest businessmen should use this tool for promoting their business in a more effective way. It is of least important if you are promoting your business digitally and don't have a physical location.
Google Maps API is easy to use. Map visibility is good and accurate. Easy to search routes, distance, and travel time based on actual address to address locations or when quoting a zip code to zip code rate. The user interface is friendly and make usage easy and quick to obtain all the information I need to properly quote and plan my driver's routes.
It does everything I need it to do and hasn't let me down yet. It has been a lifesaver for my roofing accounts. Most of my clients for the roofing belong to an Amish community with no computers and so forth. So being able to search the maps and look at the rooftops is imperative for those campaigns.
I find Holebase much more user-friendly and intuitive although have not used for as long as gINT. It seems to handle the data in a much more reliable way and I've yet to find pesky bugs. Whilst gINT feels like a polished interface to what is in essence a simple database, Holebase feels like a bespoke piece of software.
Google MAP API is one of the prominent ones as compared to others. In the selection process also we are [complete] with the API provider by Google MAP as it is quite stable.No doubt it is one of the best methods to implement or integrate as compared to any others which is available in the competition.
