-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bbox issue for some countries #50
Comments
@nnjemie Replying to the question For now, we have added custom bbox for Russia. We will also add custom bbox for those countries cc: @thenav56 |
could you please still review the various b-boxes? We still need to manually adjust the b-box data for countries that have over seas territories so that it goes to the main land, for example France and possibly the Netherlands. it seems to be fine for the UK. |
Sure @nnjemie |
UpdateWe currently have an issue with bounding boxes (bbox) due to:
To address this, we have created custom bboxes for countries and admin1 regions. This approach avoids the complex logic needed to calculate the correct bboxes directly from polygons. If the source database (i.e., IFRC) resolves this issue in the future, we can switch to their data. Country BboxesBelow are the country bboxes generated from GeoJSON provided by IFRC: Note: GeoJSON used for the image: country-bbox.json Here are the manually fixed country bboxes: Note: GeoJSON used for the image: country-bbox-fixed.json, generated from this file. Admin1 BboxesBelow are the admin1 bboxes generated from GeoJSON provided by IFRC: Note: GeoJSON used for the image: admin1-bbox.json Here are the manually fixed admin1 bboxes: Note: GeoJSON used for the image: admin1-bbox-fixed.json, generated from this file. |
Update: This has been pushed to production. If any more changes are required related to custom bbox, let's reopen this ticket. |
Issue detail and fix: #50 (comment)
The text was updated successfully, but these errors were encountered: