surely, i've been sniffing too much SQL, but your scenario seems like
a poster-child for RDBMS.
maybe the schema is usually a bit simpler, where you have a spatial
table, say a weather station, then a related data table of many
observations, but this case doesnt seem much different.
here's my go in psuedo:
survey_control (
survey_control_id INT
geom GEOMETRY
)
monument (
monument_id INT
survey_control_id INT REFRENCES survey_control(survey_control_id)
is_active BOOLEAN
)
monument_history (
monuemnt_id INT REFERENCES monument(...
event_id INT REFERENCES event(event_id)
date DATETIME
)
event (
event_id
event VARCHAR /* ACTIVATED, INSTALLED, REPAIRED, etc. */
)
On Dec 13, 2007 12:48 PM, Landon Blake <[EMAIL PROTECTED]> wrote:
>
>
>
>
> This is being sent to the geowanking and OSGEO discuss list. I apologize in
> advance if you catch it in your inbox twice, but I didn't want to miss any
> potential resources.
>
>
>
> I'm working on a GIS Data Model in which I am trying to model some temporal
> data. I've done a little research online, but most of the info is pretty
> ESRI specific. Although I'm somewhat curious about the use of temporal data
> in a GIS in general, I'm really interested in a specific approach to the
> problem.
>
>
>
> Does anyone know if there is material available that discusses using events
> to model temporal data? (Like the "events" we use in GUI programming.)
>
>
>
> I'd really like to read some "software-neutral" principles on how events can
> be used to model time in GIS if this is available. Or, if you have tackled
> this challenge personally, I'd love to learn more about your personal
> experience and solutions.
>
>
>
> Thanks,
>
>
>
> Landon (A.K.A. – The Sunburned Surveyor)
>
>
>
> P.S. – I posted about the particular circumstances that led to my interest
> in this topic and some existing material I found online at my OpenJUMP blog:
> http://openjump.blogspot.com/
>
>
>
> Warning:
> Information provided via electronic media is not guaranteed against defects
> including translation and transmission errors. If the reader is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this information in error, please notify the sender
> immediately.
> _______________________________________________
> Geowanking mailing list
> [email protected]
> http://lists.burri.to/mailman/listinfo/geowanking
>
>
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
