-
Notifications
You must be signed in to change notification settings - Fork 3
2017_11_08_ _Exploring_Storage_Mechanisms
Jaillot Vincent edited this page Nov 9, 2017
·
2 revisions
Eric, Vincent and John
- CityJSON v0.3 has been released
- Gradual transition to a complete JSON based platform? JSON messages are used between servers and clients in the form of b3dm and 3Dtiles.
- Current Use of limited temporal information (year of construction and demolition). Use of versionable abstract features for all the different types of city objects. Adding tables related to 3DCityDB related to versions and workspaces.
- Current computation of tileset
- Modifying the architecture to store tilesets and geometry information to NoSQL based data store: Gradual transition from 3DCityDB to NoSQL store for getCities() and getGeometries().
- Relooking the current implementation of tile computation to include versions and workspaces
- Implementation of processDB() needs to be changed (to incorporate NoSQL store)
TODO
- Discussion with Jeremy to get his viewpoints on personalized client space and the input arguments of processDB().
- Create an architecture including NoSQL based data store
- Computation of tileset including workspaces and versions
After discussions with JGA regarding the building server evolution and the new plans discussed in this meeting, we propose these architecture diagrams as a short term target (to merge works from VJA and JGA and to be consistent with propositions of JSA).