Comments for Tiny Geo Coder (blog)

Comment on 13 Million API Queries Later … by Problems with Managing TIny Projects

Problems with Managing TIny Projects — Sun, 16 May 2010 21:13:15 +0000

[...] we don’t think of is what happens if it gets popular. Do we open source it? Do we let others contribute to make it better? Do we try to monetize it and [...]

Comment on Downtime Resolved And Source Discovered by Nate

Nate — Wed, 07 Apr 2010 16:09:55 +0000

Harry, thank you for the comment. I appreciate that you’re using the service at all, even for your 5 queries. It makes me smile.

Thanks.

Comment on Downtime Resolved And Source Discovered by harryteguh

harryteguh — Wed, 07 Apr 2010 13:12:01 +0000

Hi, Nate.

I’d like to pay for the reverse geocoding service if I could. But, I’m using Tiny GeoCoder’s service for non-commercial use. I’ll only be needing 5 unique queries from Tiny GeoCoder for the application I am making. I’m really sorry.

Best regards
Harry

Comment on Unexpected Downtime by Nate

Nate — Mon, 22 Mar 2010 00:58:31 +0000

Thanks for your comments folks.

Comment on Downtime Resolved And Source Discovered by Nate

Nate — Sun, 21 Mar 2010 22:22:35 +0000

That’s a great point Marcel. I appreciate the comment and obviously we don’t want to hurt anyone’s business by changing the model. We’d rather find something that everyone can work with.

Thanks again.

Comment on Downtime Resolved And Source Discovered by atomton

atomton — Sat, 20 Mar 2010 10:24:05 +0000

As a regular user of your service I really appreciate it and I basically agree to a tiered package system (like Andrew suggested) or any other payment system.

But unfortunately I’d like to use the API in one or more free iPhone app(s) and can’t pay for the service without having the users to pay for it. For sure this could be an In-App-Purchase, but I guess I’d have to return to the old fashioned way to keep the apps free. And I don’t think users will pay on a regular basis just for the geocoding features.

It also depends on the amount of free requests. If it’s high enough, it could work, but I don’t think so tho.

Again, I would pay for it if I could, but making losses is not an option for me – and not for anyone else, I guess.

Cheers,
Marcel

Comment on Downtime Resolved And Source Discovered by Nate

Nate — Sat, 20 Mar 2010 05:07:25 +0000

That does make sense, and it’s very similar to what a few others have mentioned. Thanks for the input Andrew. I really do appreciate it.

Comment on Downtime Resolved And Source Discovered by andrewc

andrewc — Sat, 20 Mar 2010 03:18:40 +0000

Well, my two cents, for what they are worth, is that you set up a tiered package system. Up to x queries per day is free. Then x to y per day is $1 (for the whole day). Then y to z queries is $2 for the whole day. ETC ETC. That way, if every day I am between x and y my bill at the end of the month is $30.

Allow free use without signing up for up to x queries but then CUT OFF the queries when the max is hit.

Set up clients that want to have the ability to automatically jump in to the x-y, y-z ranges and be charged at the end of each month for this service with paypal or some other payment gateway prior to use. If they never even get up to x-y they pay nothing. Some days they might be below x, some between x-y and some between y-z etc. But they only pay the max amount each day and not y-z the whole month if they only get into y-z one day.

I hope that makes sense.

Andrew

Comment on Question for App Makers Using Tiny GeoCoder by Nate

Nate — Sat, 20 Mar 2010 02:07:45 +0000

Nick,

That’s a great set of questions. It’s true that Google is one of our data providers. It’s also true that we do have explicit permission to run the service the way we do. Your suggestion of providing a list of our API geocoding sources is a great idea and we’ll definitely add a page to display those sources and link to their TOS. Thank you for the suggestions.

Comment on Question for App Makers Using Tiny GeoCoder by Nick

Nick — Thu, 25 Feb 2010 22:53:59 +0000

I couldn’t find a list of sources for this site’s API geocoding service. The previous post says Google is one of them. Google has a TOS defined, so users of this site’s API service must also inherent google’s TOS + those of any other data sources [right?]. Can you provide a list of your API geocoding sources or a TOS.