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
It would be convenient to have a tool to convert generic aviation-related (x, y, z) GPS points to NMSIM trajectory (.trj) files. Right now tracks_within() has a specific solution when provided with a geopandas.GeoDataFrame.
Shapefiles are no problem to convert using geopandas.read_file(), but feature classes would have to be saved as shapefiles, first. An important part of this work would be assessing whether the incoming points have all/partial/none of these fields:
Elevation (MSL)
Datetime
Heading [could easily be computed]
Velocity (knots) [could be computed]
N-Number
Other changes for a general function include:
Ability to override site parameters with (x, y) point in WGS84?
NVSPL matching requirement into a boolean parameter.
Handling UTC offset automatically
The text was updated successfully, but these errors were encountered:
It would be convenient to have a tool to convert generic aviation-related (x, y, z) GPS points to NMSIM trajectory (.trj) files. Right now
tracks_within()
has a specific solution when provided with ageopandas.GeoDataFrame
.Shapefiles are no problem to convert using
geopandas.read_file()
, but feature classes would have to be saved as shapefiles, first. An important part of this work would be assessing whether the incoming points have all/partial/none of these fields:Other changes for a general function include:
The text was updated successfully, but these errors were encountered: