Jacob,

There's already a database in place on the dev server, with the data model documented at the following post.. (indeed, this data model took into account the fields you named, earlier in the same post).

http://www.horizonsunlimited.com/hub...lication-25491

Is this the sort of thing you're after? Any potential changes are still up for grabs, but it won't be long before we start committing to this model (by virtue of code we'll have built that uses it).

I'm just about to start looking at putting a Drupal front end on it, with guidance from Jeff and Grant. We could do with any help we can get.

If you want to move independently, or aren't interested in Drupal/PHP (which I'm still learning), it's probably still best to use the same data model (if possible).. that way, we don't waste time and energy with two divergent data models. It will also minimise data migration issues from one data model to the other.

The data model supports all the things you mention.. it's just a matter of putting the relevant data in the "thingtype" table, and building on a front end, to allow us to input / retrieve data. I suspect we'll need at least one generic front-end to input / query data initially. This generic screen should be able to handle any type of positional data (motels / parking / cheap motels, whatever), until we get something more specific in place for that particular type of data (which would probably be driven by demand).

Colm