How rendrom/rosreestr2coord works
rosreestr2coord retrieves geometry for cadastral codes from the NSPD geoportal and exports results as GeoJSON or KML; its CLI also supports batch processing. The graph follows the documented workflows and sampled call sites. README capabilities such as caching and plotting are not wired here because their implementation was not sampled, so they are not mapped as runtime components.
Main entry points: parser.py Area lookup · console.py CLI · batch.py Batch processor · request.py Request routing
Components 14
Entry points
- CLI
rosreestr2coord/console.py - Batch processor
rosreestr2coord/batch.py - Python API
rosreestr2coord/__init__.py
Geometry lookup
- Area lookup
rosreestr2coord/parser.py - WGS transform
rosreestr2coord/utils.py
Request transport
- Request routing
rosreestr2coord/request/request.py - HTTP adapter
rosreestr2coord/request/urlib_adapter.py - Proxy handling
rosreestr2coord/request/proxy_handling.py - Proxy file
rosreestr2coord/request/proxy_handling.py
Result export
- GeoJSON and KML
rosreestr2coord/export.py
Other components
- NSPD geoportal
- Proxy list site
- Output files
- User
Connections 16
- User → CLI: runs
- User → Python API: calls
- CLI → Area lookup: looks up code
- CLI → Batch processor: starts batch
- Batch processor → Area lookup: looks up each code
- Area lookup → Request routing: sends query
- Request routing → HTTP adapter: dispatches request
- HTTP adapter → NSPD geoportal: HTTP request
- Request routing → Proxy handling: gets proxies
- Proxy handling → Proxy file: reads and writes
- Proxy handling → Proxy list site: downloads proxies
- Area lookup → WGS transform: transforms geometry
- Area lookup → GeoJSON and KML: converts to KML
- CLI → Output files: writes results
- Batch processor → GeoJSON and KML: builds batch exports
- GeoJSON and KML → Output files: writes exports