Exploration of BCC Databases

Exploration of BCC Databases

1. Bike Rack Locations

   • Table Details
     • 7 columns
       • Varchar
       • Int
       • Decimal
     • 110 records
     • Primary Key
       • No Clear Primary Key
         • A Composite Key could be created using:
           • Latitude
           • Logitude
   • Positives
     • Clear description of location
       • Giving a word description along with a map location will ensure that location is found
     • Tells capacity of bike racks and type
       • Helps users judge whether there would be space for their bike
     • Clear location
       • The use of longitude and latitude to give a clear map location
   • Negative
     • No Clear Primary Key
       • Means only unique identifier can be found by creating a composite key
     • Low number of records
       • Clear more than 110 bike rakes in Brisbane
         • Therefore some bike racks must be missing

2. Tracks and Trails Locations

   • Table Details
     • 8 Columns
       • int
       • varchar
       • Decimal
     • 7111 Records
     • Primary Key
       • OBLECTID
     • Foreign Key
       • Park_Number
   • Positives
     • Large Database
       • Broad area of Brisbane covered
         • Gives an accurate of the path within an area
       • Covers all paths in the BCC
         • Gives an accurate of the path within an area
     • Gives surface of the path
       • Allows user to flitter between different path types
         • Increased user experience
       • Prepare users for the style of path
         • Increased user experience
     • Length of Path
       • Allows user to identify paths based on the distance they want to walk/run/ride
   • Negative
     • No location data/ unusable location data
       • No clear location data, which makes hard to match the database against a map
     • Lack of detail about paths
       • Only give path length and distance
         • Does not specify aspects like location, terrain or connecting paths
     • Requires other datasets due to the use of a foreign key
       • Requires a connecting datasets that links park_Numbers to a map

3. Community Garden Locations

   • Table Details
     • 9 Columns
       • Varchar
       • Decimals
       • int
     • 56 records
     • Primary Key
       • Garden_Name
   • Positives
     • Location Information
       • Adress
         • Allows user to find where the location of the garden is
       • Latitude and Longitude
         • Allows the location to be placed on a map with the table data alone.
     • Contact information
       • Website
         • Allows a hyperlink to be created on the page
       • Phone Number
         • Give another option for contacting
     • Detailed Data
       • 9 columns
         • Garden_Name
         • Address
         • Facilities
         • Phone
         • Website
         • Opening_times
         • Other_Information
         • Latitude
         • Longitude
       • Allows for additional information
       • Above and beyond detail
   • Negatives
     • Phone number does not follow specific format
     • Some empty Fields
       • Phone Number
         • 13/55 have phone numbers
           • Means only way of communication is through website
       • Open_Times
         • 1/55 have opening times
           • not enough data to be useful
       • Other_Information
         • 11/55 have more information
           • Not that bad, but could also be improvved on

4. Weed Identification

   • Table Details
     • 361 Records
     • 19 Columns
       • Int
       • Varchar
       • Boolean
     • Primary Key
       • Nid
     • Foreign Key
   • Positives
     • 6 methods of identification
       • Growth Form
       • Flower Colour
       • Leaf Arrangement
       • Foliage Colour
       • Flowering Time
       • Simple/Compound
     • Makes Identification Easy
       • Clear descibtions
       • Large number of identification methods
     • Large Data Set
       • 361 records
       • 19 columns
     • Applicable
       • Tells if BCC should be notifed
         • Helps to remove unwanted plants
       • Gives common name and species names
       • Family
   • Negative
     • Could cause confusion
       • No photo
         • Does not allow the plant found to be checked againist an image
       • Hard to tell the difference between some categories
         • eg. Shrub vs Tree
         • eg. Cream vs White
     • Unneeded Categories for public use
       • Council declaration
       • State declaration

5. Free Native Plants

   • Table Details
     • 37 records
     • 4 columns
       • Varchar
     • Primary Key
       • Species
         • Varchar
   • Positives
     • Long and clear descriptions
       • eg. Hardy prostrate groundcover that grows to one metre. Purple and white flowers during the summer months. An excellent spreading groundcover for a sunny well-drained position. Suitable in pots or containers.
     • Common names and species names
       • eg. Cut leaf daisy (Brachyscome multifida)
     • Detailed Columns
       • Gives clear details for the few columns
   • Negatives
     • Low number of columns
       • 4 columns
         • Description and growing requirements
         • Attracts
         • Species
         • Type
     • Low number of records
       • 37 records
         • Small database leads to low usefulness when searching for plant
     • High values within fields
       • Long Description
         • Hard to use when searching a database
       • Exceeds Varchar (255)
         • Takes more data to store

6. Bus Stop Locations

   • Table Details
     • 21 Column
       • Int
       • Varchar
       • Decimal
       • Date
     • 6328 records
     • Primary Key
       • HASTUS
   • Positives
     • High Detailed data
       • High detailed Locations data
         • Longitude
         • Latitude
         • EASTING
         • NORTHING
         • Suburb
       • Detailed description of type of bus stop
         • BUS_STOP_TYPE
         • BOARDING_POINT
         • ROAD_GRADIENT
         • CROSS_FALL
     • Common foreign keys to connect with other
       • TRANSLINK_ID
       • Allows other database to easily linked
   • Negative
     • Some bus stops don't have completed data
       • DATE_OF_LAST_AUDIT
       • NEAREST_CROSS_STREET