Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Federated Data Maintenance


Published on

Richard Jeffries and Ian Fitzgerald from Transport and Main Roads, Queensland discuss how Federated Data Maintenance can be used in maintaining a single statewide view of planning activities at MapInfo Forum 2014 in Brisbane.

Published in: Business
  • Be the first to comment

Federated Data Maintenance

  1. 1. MapInfo Forums 2014 Federated Data Maintenance Richard Jeffries and Ian Fitzgerald Transport and Main Roads
  2. 2. 2 MapInfo Forums 2014 Overview of your organisation  Transport and Main Roads  Asset owner / planner / operator  Multiple asset types – road, busways, rail heavy/light, maritime, ITS&E  Multi vendor GIS environment, Oracle spatial, MI tab sync/replication  Distributed GIS groups covering local and corporate needs  Corporate data “pushed” from head office
  3. 3. 3 MapInfo Forums 2014 Business Problem  Planning data was independently managed to different data models  Requirement to maintain a single statewide view of planning activities and their status.  Required agreement on a single data model and approach  Need for each TMR District to have control of their own planning data BUT needed access to state-wide data  Required a head office data “approval” function
  4. 4. 4 MapInfo Forums 2014 The Solution  TMR has a preference to storing spatial data within Oracle Spatial  MapInfo Pro works well with Oracle Spatial  MapInfo Pro can edit directly through an Oracle View  Oracle source is transparent to users – still only see a tab file  A single state-wide Oracle table was created  12 editable views were created, one for each District  A master “validation” view was created for the data approver  FME used to publish approved data for live use
  5. 5. Oracle View View View View View View View View View View View View Oracle F M E Other GIS Editing schema The Solution “Live” schema GI_TRANS_PLAN
  6. 6. 6 MapInfo Forums 2014 Outcomes and lessons learnt  Consult, consult, consult … a single data model needs to be agreed … early  Multi user data editing removes the dependence on a single head office data consolidation function  Utilise the GIS skills within the department  Utilise the inbuilt MapInfo capabilities in data editing  Minimise change impacts by pre building editing workspaces  Maintain the vendor neutral data sources for maximum capability
  7. 7. 7 MapInfo Forums 2014 Next steps  Utilise this federated editing concept in other data products  Empower the GIS groups in the districts to be in control of their own data … but centrally managed  District feedback and enhancements
  8. 8. 8 MapInfo Forums 2014 Questions?