Diff: services/service-fs-data-lake.es
From d0b5b58 to d0b5b58
+0 / −0 lines
| Before | After |
|---|---|
| --- | --- |
| schema: foundry-doc-v1 | schema: foundry-doc-v1 |
| title: "service-fs" | title: "service-fs" |
| slug: service-fs-data-lake | slug: service-fs-data-lake |
| category: services | category: services |
| type: topic | type: topic |
| quality: complete | quality: complete |
| status: active | status: active |
| audience: public | audience: public |
| short_description: "service-fs is the foundational storage layer for the platform's GIS pipeline — a flat-file data lake that stores raw geospatial points ingested from open sources in separate retail and civic landing zones, available immediately to every downstream service without an ETL step." | short_description: "service-fs is the foundational storage layer for the platform's GIS pipeline — a flat-file data lake that stores raw geospatial points ingested from open sources in separate retail and civic landing zones, available immediately to every downstream service without an ETL step." |
| bcsc_class: public-disclosure-safe | bcsc_class: public-disclosure-safe |
| language_protocol: PROSE-TOPIC | language_protocol: PROSE-TOPIC |
| last_edited: 2026-05-08 | last_edited: 2026-05-08 |
| editor: pointsav-engineering | editor: pointsav-engineering |
| paired_with: service-fs-data-lake.es.md | paired_with: service-fs-data-lake.es.md |
| cites: [] | cites: [] |
| --- | --- |
| **`service-fs`** is the foundational storage layer for the platform's GIS pipeline — a flat-file data lake that stores raw geospatial points ingested from open sources (OpenStreetMap, Overture Maps Foundation) in separate retail and civic landing zones, available immediately to every downstream service without an ETL step. Retail records — commercial operators, anchor stores, fuel outlets — and civic records — hospitals, universities, transport hubs — are kept in distinct subtrees so the filtering and clustering services can work on each domain independently. | **`service-fs`** is the foundational storage layer for the platform's GIS pipeline — a flat-file data lake that stores raw geospatial points ingested from open sources (OpenStreetMap, Overture Maps Foundation) in separate retail and civic landing zones, available immediately to every downstream service without an ETL step. Retail records — commercial operators, anchor stores, fuel outlets — and civic records — hospitals, universities, transport hubs — are kept in distinct subtrees so the filtering and clustering services can work on each domain independently. |
| ## Data Ingestion and Storage | ## Data Ingestion and Storage |
| The service maintains a unified filesystem structure with separate landing zones for retail and civic infrastructure data. | The service maintains a unified filesystem structure with separate landing zones for retail and civic infrastructure data. |
| - **Retail landing:** raw commercial operator records ingested from open geospatial registries (OpenStreetMap, Overture Maps Foundation). | - **Retail landing:** raw commercial operator records ingested from open geospatial registries (OpenStreetMap, Overture Maps Foundation). |
| - **Civic landing:** raw civic and institutional facility records from the same open sources. | - **Civic landing:** raw civic and institutional facility records from the same open sources. |
| ### Architectural Role | ### Architectural Role |
| As the stateful layer of the platform, `service-fs` is responsible for data persistence. It is designed to be independent of the analytical software — if the GIS orchestration layer is re-provisioned, the core data assets remain intact within this layer. The clean separation between data persistence and analytical logic is a core design invariant. | As the stateful layer of the platform, `service-fs` is responsible for data persistence. It is designed to be independent of the analytical software — if the GIS orchestration layer is re-provisioned, the core data assets remain intact within this layer. The clean separation between data persistence and analytical logic is a core design invariant. |
| ## Unikernel Implementation | ## Unikernel Implementation |
| In production, `service-fs` is deployed as a low-overhead unikernel. It provides a restricted API for the `service-business` and `service-places` intelligence layers to read raw data and write back processed results, enforcing clean separation between storage and analysis concerns. | In production, `service-fs` is deployed as a low-overhead unikernel. It provides a restricted API for the `service-business` and `service-places` intelligence layers to read raw data and write back processed results, enforcing clean separation between storage and analysis concerns. |
| ## See Also | ## See Also |
| - [[service-business-clustering]] | - [[service-business-clustering]] |
| - [[service-places-filtering]] | - [[service-places-filtering]] |
| - [[app-orchestration-gis]] | - [[app-orchestration-gis]] |