On 4/15/13 9:27 AM, Rob Warren wrote:
Richard,
The way I see it, we have two solutions:
a) Abuse the GPS trace storage of the base OSM database to store the
movements and modify the renderers to read them.
b) Implement movement through the use of multiple ways / relations,
one for each time stamped movement.
I'm tempted to use b) for troops movements and b) for "born digital"
material like AIS / GPS / radar tracks.
Are you planning to encode units as 'fronts' or as point data with
nato-style unit icons?
i'm thinking b as well.
i was planning to use nodes where the deployment was
unavailable/uninteresting
(e.g., a company marching down a road), but ways where the information
is interesting
(e.g., which way a unit was facing in combat, and whether the unit was
in line or
column at the time, or perhaps the path of a march or retreat.)
there are potentially two scenarios for using relations:
1) showing movement of a given unit over time
2) showing groupings of units into higher level units
richard
_______________________________________________
Historic mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/historic
