OpenLayers OpenLayers

Ticket #1074 (closed feature: duplicate)

Opened 1 year ago

Last modified 3 months ago

Support for temporal vector data

Reported by: ianmayo Assigned to:
Priority: major Milestone:
Component: general Version: 2.5 RC5
Keywords: Cc:
State:

Description

Functionalities

To provide support for the playback of temporal spatial data.

At least one of the vector datasets supported by OpenLayers supports time data (GeoRSS). If temporal layers were able to show a highlight/marker for the "current" data point, that marker could be moved according to the "current" date/time.

So, a path of positions could be played to portray "my cycle trek across the Rockies", a growing series of points could how "cities of the world that pass 1 million people", a growing series of polygons could show "countries that broadcast The Simsons", or a scrolling series of points could show "sightings of migrating whales".

Openlayer's perception of the current date/time could be controlled by a slider control (or external html-based control), and displayed in another control.

Interdependencies

None I can think of, it's a new dimension to the data.

Changes to API

As above.

Suggested strategies

It would be quite straightforward to extend the GeoRSS layer. I could botch the time display, and provide a text-based time input.

Hopefully someone with a "higher level" perspective of OpenLayers & software architecture could derive an approach where temporal dependency becomes either an attribute of a map (like spherical mercator), or a consistent component across the APIs.

Hey, I'm only considering temporal vectored data. Temporal tiled (WMS) data is a whole other game.

Alternatives

An array of positions/times could be maintained as a list/table outside OpenLayers. In addition to it's tiled data and a line representing a series of points, OpenLayers could have a single marker. When the user clicks on a position/time, javascript in the wrapper could move the marker to the indicated position - effectively putting a marker on the path at the "current time".

This would certainly be duplicating storage of the position data though, & OpenLayers does provide a tidy, configured place for the storage of the temporal functionality.

Sideaffects & complications

Guess I'm a little to naive in OpenLayers to recognise any at this point.

Change History

10/09/07 15:54:12 changed by ianmayo

  • milestone deleted.

More thoughts from me?

If layer of temporal vector data is going to do perform some kind of highlighting on receipt of new demanded time value, it needs to be able to quickly find that time, and ideally able to quickly search forwards & backwards from that point (for if the user is moving forwards or backwards in time).

This would mean either including the vectored data in a time-aware data structure, or to maintain a lookup list containing the time value together with a pointer to the vector item.

If we used the second strategy (maintain lookup table), it would probably make it easier to implement a table optimised for time search (doubly-linked list?). It would also make temporal awareness an ability that we can plug-in to other existing data structures.

05/28/08 03:37:11 changed by ianmayo

  • status changed from new to closed.
  • state changed.
  • resolution set to duplicate.

Duplicate of #1284

Well, this ticket covers a slightly broader capability (#1284 is just vector paths), but #1284 includes the essential supporting components such as #1395.