Finding Active Faults Near a Location
Geology AI can list the active faults around a map area. How the active_faults provider reads GEM, adds regional sources like DISS and flags coverage gaps.

Geology AI can list the active faults around a map area. How the active_faults provider reads GEM, adds regional sources like DISS and flags coverage gaps.

Geologic AI can pull the earthquake history of a map area. How the earthquake_history provider reads USGS and EMSC catalogues and filters by date and size.

Rock-type and age lookups need a small geological database on the map server. How geomap_prepare_knowledge installs it, and what it leaves to the operator.

A geology machine learning model must sit where the map server runs. How geomap_prepare_detectors installs it, and why the agent asks the user first.

Artificial intelligence in geology needs results you can check on a map. How geomap_render_knowledge_overlay draws them and flags points that land outside.

AI in geology often starts with a map legend. How geomap_enrich_legend matches one label to a broad rock family and geological eon, and where it goes wrong.

Geologic AI agents can ask what is recorded inside a scanned map. How geomap_query_map fills in bounds and labels from stored georeferencing and processing.

Geological AI agents can look up earthquakes, faults and minerals for an area. How geomap_query_knowledge picks sources, limits records and saves bundles.

AI geology work needs maps tied to real coordinates. How geomap_georeference fits 2, 3 or 4+ ground control points and reports residual and holdout error.

Machine learning in geology can find the legend, main map and other parts of a scanned map. How geomap_process_image runs YOLOv10 and what it returns.