metroinsight / citadel Goto Github PK

Authorization in Citadel

There is no meaning in the current branch setup. I will move dev-api to master once my PR is merged.

Hi all,

Before I decide where to put my module in the project, I'd like to restructure the current directory structure.

• Currently rest_api.py contains all the REST APIs (hypothetically). Each module that would reside under our app will have to implement REST interfaces (corresponding to view), which is colliding when multiple developers develop their modules. Shouldn't we separate out to individual modules?
  (ref: https://www.digitalocean.com/community/tutorials/how-to-structure-large-flask-applications)

• Moving MongoDB initiation into the specific module for metadata for modularization.

I have updated above issues in my local repository and am ready to push to the repo. If no objections, I will push it to the repo.

Here's an example geojson object containing multiple features:

https://tools.ietf.org/html/rfc7946#section-1.5

The current version of authentication is not working when there are many points (uuids) as Sandeep and I discussed. Thus,

1. I propose to limit the spatio-temporal query to always have UUIDs specified. This will limit the functionality of spatio-temp query but I'd argue it's acceptable as metadata query should be performed beforehand anyway in many cases. This may cause difficulties in visualization, which can be solved by the caching mechanism that we already have.
2. To optimize the policy iteration, I suggest changing the policy's data structure from JsonArray to Map<String, JsonObject> where String is for UUIDs. This will avoid iterating all the policies (which can be significantly many as time goes on) but we can only look for the necessary UUIDs' policies. It does not harm the performance in the current design also even without the proposal 1.

lng lat order is incorrect here. I am fixing it inside my code (citadel-virtuoso) merging citadel-sandeep.

We should have a EULA for the rest service, map, and any other service we create that provides data. Can use text from WIFIRE Firemap EULA (https://firemap.sdsc.edu/liability.txt),

It would be nice to log all requests to the api.

One possibility is Google Analytics: https://cloud.google.com/appengine/docs/flexible/python/integrating-with-analytics

Currently assuming IPs in order.

Do not use String for data types with specific purposes, here policy. Rather use Enum.

TODO: Fill the list of features.