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
feat(road-comparison): add indicator for road comparison #778
Conversation
… in calculate function
…ch were not yet adapted
…ets to be JSON serializeable
Preprocessing and Calculation Done. All tests are done and not failing. |
To use this indicator in the dashboard as long as no data (including coverage) is on the server, the coverage and preprocess function are commented out and mocks written instead. Therefore, test are failing at the moment as some check the result when the indicator is queried outside of the coverage area, but atm. it is mocked to always be within he coverage. Once data is on the server, remove the two lines of mock return in the functions and comment the real function content back in. With this, the tests should not be failing anymore |
…dataset.yaml and using them in the indicator
…g comparison uses global building table
…o hover Info as well. removed unused ohsome query and made use of processing date per dataset instead
Description
Adds an indicator which queries the length of road data in an AoI based on Microsoft Data and how much of it is covered by OSM data. Based on this ratio a quality estimation is made.
For this, the OQAPI DB is restructured, which is why with this PR also the name of the DB table for the building comparison indicator was changed
Corresponding issue
Closes #
New or changed dependencies
Checklist
main
(e.g. throughgit rebase main
)Please check all finished tasks. If some tasks do not apply to your PR, please cross their text out (by using
~...~
) and remove their checkboxes.