Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for dynamic geospatial map automated testing #802

Open
Brendan-Hillis opened this issue Oct 14, 2024 · 0 comments
Open

Support for dynamic geospatial map automated testing #802

Brendan-Hillis opened this issue Oct 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Brendan-Hillis
Copy link

Brendan-Hillis commented Oct 14, 2024

Is your feature request related to a problem? Please describe.
One cannot test dynamic geospatial map restrictions with interUSS automated tests.

Describe the solution you'd like
The currently provided geospatial map automated testing interface is superb at testing static restrictions (e.g. airports, national parks,...). However there are also restrictions which are dynamic in nature (e.g. Temporary flight restrictions (TFRs) in the US, Emergency/Fire feeds in AU) which we cannot test today. These dynamic feeds cannot be incorporated into the test in a similar manner to the static geospatial feature checks since by their nature they are dynamic.

  • Initially I believe limiting this scope to geoJSON source would cover the majority of feeds.
  • Priority 1 for a homogenous restriction souces (e.g. every geometry results in a block) Notional feature would be to have interUSS consume the authoritative source and for each feature in the feature collection extract the centroid of that geometry/point and use that as a dynamic geospatial feature check.
  • Priority 2 for a non-homogenous restriction source (e.g. logic applies to if the geometry is a block/advise/neither) InterUSS could be given the criteria for what parameters equate to a block/advise/neither. Note this would only work if ALL the data required to determine block/advise/neither was within the authoritative source.

Describe alternatives you've considered

  • No solutions attempted.

Additional context

  • Something to consider is the potential for an acceptable difference between the USS and the authoritative source since these dynamic sources typically come with a minimum refresh period from the regulator (e.g. 15 minute).
  • Initially would expect to work with publicly available data sources, but in the future would need to support authentication with private data sources.
@Brendan-Hillis Brendan-Hillis added the enhancement New feature or request label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant