NQ Dry Tropics ([url removed, login to view]) is a not-for-profit organisation that promotes sustainable natural resource management. We are working with shires (local governments) in our region to contain and eliminate priority pest weeds species.
Land Managers within these shires are required to provide Annual Pest Management plans to describe the weeds they have on their properties, where they are and their action in the coming year to contain or eliminate these. For over ten years these have been produced as paper reports that have are stored in file systems and reviewed each time a property is visited.
We want to be able to have these reports completed as an online form (submitted through a login and password).
We have developed a prototype web portal [url removed, login to view] - login : test : password test.
Each property is defined by a lot/plan (All Lot Plans for our region have already been created in a MYSQL database). Attributes for a property are Property Name, Owners Name, Lot, Plan, Address, and Shire. Properties can be added and deleted (this should be limited to Shire that logged user is from or administrator).
When a property is selected it will display a KML on a Google Earth Map showing extent of the property (attributes for lot plans are stored in the MySQL table). A user can then add paddocks (called parcels) which can be digitised (on a Google Map).
Weed records can then be added for each of these paddock records. There can be more than one weed record per property.
So that is it for data entry.
We then want to be able to view records in a table and map and be able to filter each by Shire, Weed Type and Property.
We want to also have the ability for users to downloaded entire shire data as KMZ/KML and ESRI Shapefile
There is also an administrator interface which will allow user accounts to be created and deleted
We would like to have the ability to add photographs. Building a mobile site for iPAD/iPhone entries would also be beneficial.
The person that we had to create the prototype to date is no longer available - but can be contacted by email to clarify code used.
There are a number of bugs in the current interface.
Whoever takes on this project will need to have the build to pretty the whole interface up (CSS etc) and be able to build the functionality (as outlined).