Add Nominatim API for load_overture_data by a parameter place_name
#115
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.
Description
This pull request introduces the Nominatim API to support place-based queries, add topological clipping for network data, and provide new utilities for removing isolations.
Boundary and area handling improvements:
get_boundariesfunction to retrieve polygon boundaries for named places using Nominatim geocoding, enabling place-based queries inload_overture_data.load_overture_dataand_prepare_area_and_bboxto accept and process a wider range of area types, including bounding boxes, polygons, multipolygons, GeoSeries, and GeoDataFrames, with automatic CRS handling and mutual exclusion with place name. [1] [2] [3] [4]Graph processing and clipping utilities:
clip_graphfunction inutils.pyfor topological clipping of network graphs, preserving network integrity when clipping segments, and integrated it into_download_and_process_typefor segment data. [1] [2]remove_isolated_componentsto filter graphs to their largest connected component, improving downstream graph analysis. [1] [2]Robustness and usability enhancements:
_download_and_process_type, including parsing stdout and filtering for valid geometries and exploding MultiLineStrings. [1] [2]process_overture_segmentsfor missing or geographic CRS, guiding users toward best practices for spatial analysis.These changes collectively make the package more flexible, robust, and user-friendly for spatial data analysis and network graph operations.
Related Issues
#114
Checklist