The problems is... defining the problem!
Top five questions about BC Spatial (I've been asked them and I've been asking them myself):
- What is it?
- What problem is it intended to solve?
- How will you do it?
- How long will it take?
- What will it cost?
Here's a brief hit list of problems that I've heard attached to the BC Spatial solution:
- Discrete and non-integrated sources of parcel data
- Incomplete or high-latency publication of member data
- Insufficient information about data (metadata) to determine fitness-for-use
- Overlapping contributions from adjacent jurisdictions
- Structural inconsistencies within and across datasets
- Absent notifications of (detailed) spatial changes
- Many of us have witnessed versions of these very good ideas planned and even initiated before - only to fall apart or not gain traction. They're either massive re-engineering tasks requiring substantial commitment, participation and reconciliation and fall down through the sheer enormity of trying to satisfy all business requirements, or they become overly insular in their approach and fail to provide significant value.
- Whose problems do these approaches solve? Some or all ICIS members? Data producers, data consumers or both? If there is conflict, who decides on the priority?
It seems to me that a reasonable approach to all of these problems is to address the needs that are common to all members (consensus ensured!), to quantify problems that are anecdotal right now, and to improve and standardize existing services that are already being relied upon. These are the guiding principles of the BC Spatial phase 1 work plan, which includes:
- BC parcel data assessment - where are there data quality, overlap or redundancy issues? When we can see it and count it, we will be in a better position to decide what to do about it.
- Automate data processing - get member data in, up, stitched, packaged and distributed through repeatable automation. Pilot the automation with a subset of members and datasets to understand the automation effort.
- Standardize the database - not just the ol' parcel layer, but its metadata - how complete is it, what is its integrity, etc. Pilot the data model through the automation pilot.
- Plan. Let's review what we've achieved and target further development on real assessment of data issues and quantitative statistics of service improvements.
Labels: requirements
