Drupal Module would be nice

[ab_connor]

I think it would be a good idea to write a module for the CMS Drupal,
which connects both possibilities. For example the module could offer
a field to fill in a geocode and then gives it to geotoad, which makes
the query. The details of the result is sent back to the module and
then saved in a node. Unfortunately I'm not able to write such code.
Maybe anyone here?

Greetings,
Andreas

[Steve8x8]

At first glance, an interesting suggestion.

But.

- How many users would actually use this, let's call it: add-on?
It's a bit tricky to count the total of GeoToad users:
359 downloads from GoogleCode for 3.14.6 but 1320, and still counting, for 3.14.4.
I've got no means to count SVN checkouts. (Ideas, anyone?)
Is this a user base wide enough?

- Behind the web interface, there would be a gc.com account. Do you really want to jeopardize yours?
Imagine someone to ask for all caches in Utah, by accident or intentionally. There are 23k+ of them. Guess what will happen.

- What will happen if someone already fetched some cache descriptions which haven't aged enough yet to be replaced in the file cache? A subsequent user will not get "fresh" stuff then (and be confused about it). What about PMO stuff?

- One of the advantages of GeoToad, to me, is to run queries in more or less unattended mode. What's the advantage of integrating it into a web interface? (Note that even the TUI, with its 24 input fields, cannot cover all application cases. Command line rulez.)

- I'm no drupal wizard, either...

Anyone?

[ab_connor]

> - How many users would actually use this, let's call it: add-on?
> It's a bit tricky to count the total of GeoToad users:
> 359 downloads from GoogleCode for 3.14.6 but 1320, and still counting, for
> 3.14.4.
> I've got no means to count SVN checkouts. (Ideas, anyone?)
> Is this a user base wide enough?

I think that a drupal module would spread geotoad. There are a lot of
drupal based sites and many geocachers, looking for integration of
geocaching.com to their sites, as long as geocaching.com would not
publish an API (maybe never?).

> - Behind the web interface, there would be a gc.com account. Do you really
> want to jeopardize yours?
> Imagine someone to ask for all caches in Utah, by accident or
> intentionally. There are 23k+ of them. Guess what will happen.

Granted, but in Drupal "Nodes" are user-based, so it is possible to
define an account for each user to use. The main idea to write this
module is also to provide personal databases of caches with your own
notices with very limited access.

Thanks for your helpful hints so long!