# flight track timestamping

**URL:** <https://discussions.flightaware.com/t/flight-track-timestamping/1683>\
**Category:** Feature Requests and Ideas\
**Created:** [July 5, 2006, 2:59pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683 "2006-07-05T14:59:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fche](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/fche/32/31471_2.png) [@fche](https://discussions.flightaware.com/u/fche)\
**Post date:** [July 5, 2006, 2:59pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683/1 "2006-07-05T14:59:53Z")

</div>

It would be nice to look at a flight track log (with positions, ground speeds) and a correlated map (with the locus of points). Not just that, it would be nice if one could click on rows on the log, and have the corresponding segment on the map highlight… or some other method to encode passage of time onto the track graph.

---

<div class="post-metadata">

**Author:** ![damiross](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@damiross](https://discussions.flightaware.com/u/damiross)\
**Post date:** [July 5, 2006, 3:31pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683/2 "2006-07-05T15:31:41Z")

</div>

Sounds like this might have already been done using Google Earth. Use the search function at the top of every forum page to look for this.

---

<div class="post-metadata">

**Author:** ![fche](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/fche/32/31471_2.png) [@fche](https://discussions.flightaware.com/u/fche)\
**Post date:** [July 5, 2006, 3:35pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683/3 "2006-07-05T15:35:21Z")

</div>

> [@damiross](#):
>
> Sounds like this might have already been done using Google Earth.

Perhaps so, but flightaware should not be dependent on google earth.

---

<div class="post-metadata">

**Author:** ![damiross](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@damiross](https://discussions.flightaware.com/u/damiross)\
**Post date:** [July 5, 2006, 3:41pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683/4 "2006-07-05T15:41:59Z")

</div>

> [@fche](#):
>
> > [@damiross](#):
> >
> > Sounds like this might have already been done using Google Earth.
> 
> Perhaps so, but flightaware should not be dependent on google earth.

It’s spelled **F** light **A** ware and **G** oogle **E** arth.

Why reinvent the wheel? Google Earth is fantastic for mapping.

---

<div class="post-metadata">

**Author:** ![fche](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/fche/32/31471_2.png) [@fche](https://discussions.flightaware.com/u/fche)\
**Post date:** [July 5, 2006, 3:47pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683/5 "2006-07-05T15:47:05Z")

</div>

> [@damiross](#):
>
> t’s spelled **F** light **A** ware and **G** oogle **E** arth.

Thanks for the spelling lesson.

> Why reinvent the wheel? Google Earth is fantastic for mapping.

Yes, but it involves running local proprietary, limited-portability software, quite unlike a web browser.

---

<div class="post-metadata">

**Author:** ![damiross](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@damiross](https://discussions.flightaware.com/u/damiross)\
**Post date:** [July 5, 2006, 3:56pm UTC](https://discussions.flightaware.com/t/flight-track-timestamping/1683/6 "2006-07-05T15:56:32Z")

</div>

> [@fche](#):
>
> > [@damiross](#):
> >
> > > Why reinvent the wheel? Google Earth is fantastic for mapping.
> 
> Yes, but it involves running local proprietary, limited-portability software, quite unlike a web browser.

I agree with you on the proprietary side of the software but disagree with the limited portability of it. I would say the vast majority of Internet connected computers are able to use Google Earth.