-
database design - api requirements
last modified February 14 by arneke
What lives where?
OpenPlans.org
- User data
- Users permissions / project memberships
- Projects
- Project metadata (extent etc, probably needed to embed map)
GeoServer / Postgis
- Data for notes / objects, with location
- Data for how to to format the markers
Postgis table design
Suggested implementations
One table per project
Pros
- Nice separation
- Possibly faster
Cons
- Insert logic becomes more complex
- Tricky if we want to show data from multiple projects
- More open files on server
One table for everything
Pros
- All operations are on rows
- Easy maintenance, say a spammer hit multiple projects
- Don't have to create tables from openplans on project creation, or have fancy on-demand code
Cons
- Spatial scans slightly more expensive
- Less separation between projects
Markers
Should markers be enumerated or free values (alt text + URL to image)?