This document describes the technical underpinnings for proposed reporting features in the CAPRA GeoNode. A functional specification for these features is available elsewhere in this SVN repository.
Todo
Document how to add new plugin types for extending basemaps to include new layer types.
(The original entry is located in geonode-core/basemap/client.rst, line 39 and can be found here.)
Todo
This page is intentionally vague, since the details of those server-side maps have not been fleshed out yet.
(The original entry is located in geonode-core/basemap/server.rst, line 11 and can be found here.)
Todo
Determine whether GeoWebCache is able to truncate its caches when layer styles change.
(The original entry is located in geonode-core/data-styling.rst, line 23 and can be found here.)
Todo
Does the featured field belong on Map records, or should it be an extension to the base map editing functionality?
(The original entry is located in geonode-core/map-application.rst, line 30 and can be found here.)
Todo
Is there a maximum allowable zoom level?
(The original entry is located in geonode-core/map-application.rst, line 39 and can be found here.)
Todo
Since the group field only has one respected value, should we collapse it to a boolean flag instead of a string?
(The original entry is located in geonode-core/map-application.rst, line 69 and can be found here.)
Todo
Do we need to support any layer types aside from OWS?
(The original entry is located in geonode-core/map-application.rst, line 88 and can be found here.)
Todo
Investigate the Piston Django extension for simplifying the implementation of this API
(The original entry is located in geonode-core/map-application.rst, line 133 and can be found here.)
Todo
Elaborate on the meaning of the map configuration options
(The original entry is located in geonode-core/map-viewer.rst, line 54 and can be found here.)
Todo
Identify further fields from the ISO standard that we need to maintain.
(The original entry is located in geonode-core/metadata/model.rst, line 31 and can be found here.)
Todo
How do we handle this and other differences between development and production installations of the GeoNode?
(The original entry is located in geonode-core/proxy.rst, line 26 and can be found here.)
Todo
Outline the authentication plugin in more detail.
(The original entry is located in geonode-core/users/sharedauth.rst, line 20 and can be found here.)
Todo
Choose an architecture for the authentication backend.
(The original entry is located in geonode-core/users/sharedauth.rst, line 40 and can be found here.)
Todo
Discuss Django hazard record layout with the client (Oscar) to ensure that it properly models the task at hand.
(The original entry is located in reporting-application/category-application.rst, line 55 and can be found here.)
Todo
Verify that these parameters are sufficient to fill out the report data.
(The original entry is located in reporting-application/data-aggregation.rst, line 18 and can be found here.)
Todo
Elaborate on these upload options to try and reach a conclusion.
(The original entry is located in geonode-core/data-upload.rst, line 32 and can be found here.)
Todo
Determine if the upload process integrates at all with GeoNode extensions such as the Hazard Reporting Category Django App.
(The original entry is located in geonode-core/data-upload.rst, line 36 and can be found here.)
Todo
Determine the format of the metadata file.
(The original entry is located in geonode-core/upload/views.rst, line 25 and can be found here.)