Closed jchudge closed 1 year ago
Regarding #2, and #3
I'll address the #1 question separately.
Sorry for the late reply.
I can't provide a direct schema but i can provide a description of the division of storage/state in the open source version. The iOS client stores markers , routes, and all user preferences. It also stores cached OSM data as retrieved from the service. This is all stored in a realm database.
In contrast, the service retrieves OSM data from one of the OSM mirrors, processes it using IMPOSM3 -- storing it in a Postgres database. Upon tile request to the service (in sources as 'gentile.py', this service uses a PostGIS sql query to retrieve the data that applies to that tile and transforms it to GeoJSON.
There are no acccounts, no PII storage, no concept of individual users as seen by the core service, and no sharing via a centralized service.
There was an additional web service that was used for some web authoring scenarios but consuming one of those routes, just inserted it into the local storage.