Should I use GeoDjango for mapping a floor plan?

Question

I want to create a floor plan map of an interior space that has clickable regions. My first thought was to investigate GeoDjango since its the mapping app for Django. But considering the dependencies, the learning curve and overall complexity, I'm concerned that I may be trying to swat a fly with a bazooka.

Should I use GeoDjango for this, or should I just store integer lists in a database field?

EDIT: The floor plan would be fairly simple; a collection of walls and workstations with the ability to define regions for how much space the workstation occupies, thus allowing offices to be defined as well as open plan layouts.

Answer 1

I'd say that using GeoDjango for this purpose is definitely overkill.

It could be implemented simply with an image map, or Canvas/SVG or Flash for extra pretty-points :)

Answer 2

IMHO using GeoDjango for a floor plan isn't a bad idea. But if your data does not change much and the amount of data (rooms, areas, workstation, ...) isn't very large, then you might not need a database and a full GeoDjango stack.

A simpler solution would be using OpenLayers directly with an image of the a (maybe scanned) floor plan as background layer. OpenLayers lets you also define region and points (markers) which handle "mouse over" or click events.

An example of using OpenLayers for a floor plan is Office Plans via Open Layers.

Answer 3

How often will the floor plan change? From your description a simple image with a imagemap would suffice.

Answer 4

One good motivation for using of GeoDjango may be:

the access to the geographical cooridinates backend, 

and you won't produce just beauty looking images with arbitrary scale, but objects which will be geo-oriented, what is cruciall if you will plane to use the created plan for purpose of indoor navigation.

I will consider strongly usage of GeoDjango, and some OpenLayers with support for GeoJSON.