Difference between revisions of "Paris Code Sprint 2016 : iTowns Agenda"
Jump to navigation
Jump to search
(Jeremy's objectives) |
(added details) |
||
Line 7: | Line 7: | ||
Code | Code | ||
− | * Load building from a bounding box hierarchy structure | + | * Load building from a bounding box hierarchy structure. This requires: |
+ | ** New alternative class to quadtree, the bounding box hierarchy | ||
+ | ** Converting GeoJSON to ThreeJS geometries | ||
+ | ** New providers for GeoJSON data and Oslandia's [https://github.com/Oslandia/building-server building server] | ||
+ | ** New tile type for the buildings | ||
+ | ** Enable a hierarchical structure to display all of its data instead of only the leaves | ||
* Generalise the node processing in the browseTree and nodeProcess classes | * Generalise the node processing in the browseTree and nodeProcess classes | ||
Latest revision as of 06:56, 19 February 2016
Proposed topics for iTowns for the Paris Code Sprint 2016.
Qualify
- Integration of iTowns and Greyhound / Envine
Code
- Load building from a bounding box hierarchy structure. This requires:
- New alternative class to quadtree, the bounding box hierarchy
- Converting GeoJSON to ThreeJS geometries
- New providers for GeoJSON data and Oslandia's building server
- New tile type for the buildings
- Enable a hierarchical structure to display all of its data instead of only the leaves
- Generalise the node processing in the browseTree and nodeProcess classes
Discuss
- See discussions on PointCloud's agenda : https://wiki.osgeo.org/wiki/Paris_Code_Sprint_2016_:_Point_Cloud_Agenda