Using GeoJSON within Areas API #93
Description
Problem description
With the introduction of the Service Areas Discovery API (e.g., POST /retrieve-service-areas), the underlaying transformation function (CSP implementation) needs to perform geographic search operations, such as:
point‑in‑area
area‑overlap
area‑coverage
These are standard GIS operations, but the current CAMARA’s custom geometry model is not compatible with the search capability offered by GIS engines and spatial databases that CSPs use internally.
The current CAMARA Area datatype (CIRCLE/POLYGON with a custom schema) was originally adequate for simple geofencing-like use cases [location-retrieval API (Device Location), region-device-count API, NetworkSliceBooking API,population-density-data API, dedicated-network API, MostFrequentLocation API].
Possible evolution
Use GeoJSON RFC 7946 instead of the existing Area data type from Commonalities.
Alternative solution
Additional context