-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GeoJSON Layers to Project #1454
Comments
I have updated the requirements (that were living on the wiki). I have simplified them removing the case of adding GeoJSON layers available for all projects within the org, and now they are linked to specific projects as resources. |
Updated format: Problem StatementBy default Cadasta provides users with OSM maps and Digital Globe imagery as default basemaps, and in addition we are working to provide the capability of adding layers via WMS #1476. But on top of that, it will be useful for the users to add additional GeoJSON layers to show specific information related to the project extent (typically cartographical layers, resources within a community, etc). Context / Use CaseA partner using GeoJSON files to load cartography layer information on top of the basemap. User Stories
DescriptionAdding a GeoJSON file to my project
Removing a GeoJSON file
Enabling GeoJSON Layers
ReferencesGeoJSON spec |
Updated format:
Problem Statement
By default Cadasta provides users with OSM maps and Digital Globe imagery as default basemaps, and in addition we are working to provide the capability of adding layers via WMS #1476. But on top of that, it will be useful for the users to add additional GeoJSON layers to show specific information related to the project extent (typically cartographical layers, resources within a community, etc).
Context / Use Case
A partner using GeoJSON files to load cartography layer information on top of the basemap.
User Stories
Description
Adding a GeoJSON file to my project
Removing a GeoJSON file
Enabling GeoJSON Layers
References
GeoJSON spec
The text was updated successfully, but these errors were encountered: