You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we are considering modeling a Trip in FtM, the thought occurred to me that, like an Address has a lat/lon, a Trip could/should have a polyline geometry to record not just start and end destinations, but the actual trajectory. I can imagine a number of cases where modeling this might be advantageous. One potential is to document a trip's trajectory - a flight, a vessels path from port to port, the path of a person (timeline?). Another might be to support more interesting UI components if we have map views in Aleph.
I am throwing this out there, but I am sure I am overlooking a number of things that make this more complicated than I am imagining it :).
The text was updated successfully, but these errors were encountered:
I'd be a bit careful with randomly committing to support geo features in FtM. Doing so would be a significant (year+) amount of effort and I would be willing to bet a good case of beer that it would make Aleph totally collapse with complexity.
As we are considering modeling a Trip in FtM, the thought occurred to me that, like an Address has a lat/lon, a Trip could/should have a polyline geometry to record not just start and end destinations, but the actual trajectory. I can imagine a number of cases where modeling this might be advantageous. One potential is to document a trip's trajectory - a flight, a vessels path from port to port, the path of a person (timeline?). Another might be to support more interesting UI components if we have map views in Aleph.
I am throwing this out there, but I am sure I am overlooking a number of things that make this more complicated than I am imagining it :).
The text was updated successfully, but these errors were encountered: