-
Notifications
You must be signed in to change notification settings - Fork 7
Issues and Questions
kat edited this page Apr 18, 2017
·
5 revisions
- How should we treat Resources with the QGIS plugin? What is a workaround and what is a long term solution? (having a consistent URL where you can simply change the resource id could be a start)
- Is it possible to automate the JOIN with the relationships and party csv files?
- Merge conflicts/version control? When you pull down a project and then pull it down again, the plugin pulls down a fresh project. Is there any way for it to see that the project has already been pulled down?
- This is a fix we likely need on the Cadasta side
- What QGIS version is supported?
- What does user permissions look like?
- BIG: Create Project -- running into issues with uploading custom fields. Are text fields the default option? Any way to add integers and select choices to the field types?
- Contact window does not pull in information until click "Update Project"
- Error Messaging:: should have better error handling ===> Received an unclear error when I had an empty project-- projects with no description or no records error out?
- Required Fields on Project Creation/Update--> TO DO: Remove Project URL requirement
- Project Names should have org name as well (for those partners that work with multiple orgs)
-
Project List :: alphabetizes by capital and then by lower case ==> Cadasta Bug: I think this is done on the API side; we may want to adjust that so that it is cap insensitive?
-
Cleaner User Interface
- window sizing: takes over whole height of screen
- Grid View: would prefer steps to be top-down rather than right-left. For example, when you pull down the project list, you must click on the "Get Available Projects" on the right and then choose a project on the left. Not intuitive for countries that have left-right languages.
- Change the sizing of some of the text boxes-- some are massive.
- Add padding to the buttons
-
Layer Support
- Would be nice to upload multiple layers...like gpx traces... but there is a workaround, which is to merge files and convert to shapefiles...
-
Styling Packages
- Can we package styling rules for partners? Based on symbology column? That may be an issue...
- Cadasta TO DO: Create rule-based styling... list of points... list of polygon categories
- Grey out the text box that lists logs after the Submit button