ABN: 32 991 550 356
[ Home | Services | Downloads | Contact ]
![[Dividing Line Image]](images/div.gif){kind=small}
Mapping is the spatial representation of data. Textual information relating to the spatial data (ie its position, description, attributes etc) can either be stored within the mapping programme itself or in a relational database.
I have been using MapInfo on an almost full-time basis since 1998, have undertaken advanced training in its capabilities and have gained experience that can only come from frequent intense use of the product. Most of my mapping experience has been in the natural resource management (NRM) field, including weed mapping, vegetation mapping and fence line locations (using GPS). I have also had considerable experience in the production of GIS-based Planning Schemes.
During these activities, I developed a number of database applications using Microsoft® Access (97 and 2000/XP) to fill specific data handling requirements. One of these databases was developed for a State-wide weed mapping project (which was distributed through a network of government and private weed officers), while the other was developed to track revegetation, fencing and other field work associated with an NHT Landcare project in the Southern Midlands of Tasmania.
I have undertaken advanced training courses in both Microsoft® Access (which utilises Microsoft® VBA (Visual Basic for Applications)) and Microsoft® Visual Basic.
Common desktop mapping applications (MapInfo, ArcView, etc) suffer from the disadvantage of not having a relational database built into the programme. Relational databases such as Microsoft® Access don't normally have mapping capabilities built in.
One solution is to have a key field identifier contained in both a MapInfo table and an Access table (say) and utilise a hyperlink capability to display data from both applications. This solution does not take advantage of the full capabilities of a robust relational database (which Access is) because the link can only be to a single table in the database (a flat table, in jargonese).
A well-constructed relational database application, on the other hand, has several tables, all containing specific types of information on a specific item. For example, a database keeping track of an revegetation project may have a table that contains descriptions of specific projects, another table that contains details of plants ordered for that project, another that contains details of site preparation required for the project etc - all linked by a common identifier (say, the project number). A desktop mapping application (in their various current versions) cannot access all this data.
An alternative solution is to develop a standalone application that combines the best of both worlds, utilising the strengths of a relational database with the spatial depiction of a desktop mapper.
In collaboration with one of my Associates, we are developing a standalone application that will do just that, without the need for a full-blown GIS programme or the need for a full relational database application, but with the ability to record both the textual and the spatial information required to fully describe a particular entity, such as a revegetation project or a risk management project (see my Risk Management page).
I can also offer distribution of and support for a range of innovative mobile mapping solutions for the capture, management and auditing of spatial data, utilising the proven MapX Mobile and .NET technologies and developed by this Associate. These products are in use in Tasmania for such activities as walking track maintenance and as a mobile front-end for MapInfo-based asset management applications and can be tailored for specific needs (see my Software page).
I am a Foundation Member of the Spatial Sciences Institute and presented a paper on the use of spatial data in emergency risk management, based on "The Tasmanian Emergency Risk Management Project" as a case study, to the recent Queensland SSI Conference (April 2004 in Brisbane).
Wide-ranging and extensive experience in mapping activities (natural resource management, risk management, planning schemes), especially in the MapInfo desktop mapping programme but also in more robust GIS packages such as SPANS; Database development experience utilising VBA, Visual Basic and the Microsoft® Jet database engine for natural resource management and emergency risk management applications; Linking of spatial and textual information; Provision of innovative and robust mobile mapping solutions based on MapInfo technology Provision of front-end solutions for recognised asset management mapping applications such as BizeAsset Provision of front-end solutions for customised stand-alone asset management mapping applications
[ Home | Services | Downloads | Contact ]
![[Bullet]](images/bullet.gif){kind=small}