Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
At the request of firefighters, we have added API calls to automatically retrieve location details based on triangulated coordinates. This includes identifying the city and, when available, the corresponding ONF forest parcel number
The get_location_info(lat, lon) function first performs reverse geocoding using OpenStreetMap’s Nominatim service to extract administrative information such as the city, country, and country code. If the location is in France, the function then queries the national forest parcel database (hosted by IGN) to check whether the point intersects with a public forest parcel managed by the ONF. If so, it returns the full parcel attributes