-
Notifications
You must be signed in to change notification settings - Fork 7
FOEP0001 Points of Interest
The author uploads a set of locations and information (audio, visual, textual) relevant to each location, that information will be available to the user in the app.
The author uploads a set of locations where he is interested in collect some information and the format of the observation required, the user of the app is made aware of that interest.
An author wants to validate information previously captured, this can be achieve in several ways:
a. Creating a new observation in the same location of the observation to validate b. Editing/Correcting the observation to validate c. Editing a copy of the observation to validate
The cartographic features uploaded for the author are converted to a geoJSON, the most popular formats will be available (geojson, shapefile, kml, kmz, csv), the related assets can be uploaded as a zip files or individually and it will be available as downloadable assets from the backend.
-
Scenario A - For fullfilling the requirements of this scenario a new type of assets is needed: a CARD, a piece of html content with relative reference to its assets, it's a common metaphor that could be easily implemented in any ui framework. BB: see below for overview of Card design in Android https://www.google.co.uk/design/spec/components/cards.html# is idea to link cards to a form in order to edit them?
-
Scenario B - Notifiying and opening an editor when the user is in the range of a location is available in the geofences plugin, a geofence could be enable for each PoI if it's desired but in that case the Authoring Tool should only know about PoIs and let the user decide if the PoI is going to behave in an passive or active (registering as a geofence) way. BB: so if user does not want form to trigger with geofence - can user simply touch pin to open form?
-
Scenario C - Enable the record editing and the record download is needed and more discution about the lifecycle of the record.