Cooking up a national SDI framework

Today saw the release of the spatial data infrastructure (SDI) cookbook for New Zealand – a pretty exciting step along our path to a national SDI.

This initial version of the NZ SDI cookbook has been developed to provide guidance for the early stages of implementing SDI, with the chapters based on what is currently known about the elements typically underpinning SDIs, and guided by developments and experiences in jurisdictions internationally.

It includes technical guidance around standards and implementation to help organisations recognise and realise components that together, help shape their contribution to New Zealand’s SDI. In its current form, the cookbook provides context and guidance for the introductory phase of the SDI, describing minimum requirements to help support participation at this early stage.

What has been particularly exciting for me in pulling the cookbook together has been the degree to which we have seen collaboration across central and local government, industry and academia to help shape the concept of SDI into more of a reality. Many hands have contributed to this document, and our hope in releasing it is that many more people will be involved in giving feedback and suggestions to further refine the content.

This is by no means a complete or perfect document, but it’s much easier to start from somewhere. Some components of SDI we know well – the need for agreed standards to underpin interoperability for example. Others are new concepts for many of us – such as the roles of data stewards and custodians.

To further shape the guidance we’re making available, we will be sending out a Request for Information soon, asking solution providers to supply product-specific guidance to enable users across New Zealand to effectively participate in a spatial data infrastructure. Once the responses to this RFI have been received, they will form chapter six of the cookbook.

I encourage everyone to comment, give feedback and email us your thoughts. We’re considering what other channels we can establish to capture your thoughts and discussion on the content included, so we welcome suggestions on this also.

We will also be engaging with the wider community to develop a ‘user forum’ type environment for ongoing discussion and revision of cookbook content to ensure its relevance and currency.

Until we establish these more formal channels – please feel free to leave comments on the cookbook through the comment function for this blog post, with a reference to the particular cookbook section if needed.

Also, you can email the NZGO team on nzgo@linz.govt.nz with your feedback, and any questions you may have.

Kevin Sweeney

Geospatial Custodian
New Zealand Geospatial Office

Comments

Kevin, I've blogged on the

Kevin,
I've blogged on the cookbook and subsequent RFI process here:
http://cameronshorter.blogspot.com/2011/07/project-overviews-quickstarts...

and followed up with:

... I'm excited to think that the resulting SDI Cookbook has the potential to become a very valuable resource not just for New Zealand, but for other countries as well. But what I'm particularly interested to see is where this SDI Cookbook will go from here. How will the Cookbook be updated and maintained as technologies improve? Will community feedback be collected? If so, how will it be applied and resourced? How will NZGO balance broad crowd sourced information verses quality review cycles? Will the Cookbook be extented into other areas, such as training? Will other countries collaborate with New Zealand in extending and maintaining the Cookbook, or will rival Cookbooks be developed? These are some of the questions I've been raising with NZGO, and which I believe will determine whether the SDI Cookbook will become wildly successful, or will just briefly be a useful document for a while in New Zealand.

Thank you for the feedback on

Thank you for the feedback on the Cookbook Jim, and your interest in staying engaged in its development. If we here in the NZ Geospatial Office do our jobs well, there will be plenty of options to participate in the ongoing development of our thinking and guidance around SDI.

One of the goals of this initial version of SDI guidance was to simply introduce web service options for making data widely available. Within that context there are recommendations but not a constrained approach to particular types of web services.

A key component of introductory SDI, supported by this version of the Cookbook, is promoting SDI participation generally. We therefore empahised simpler options like WMS but not to the exclusion of other options like WFS. WFS is listed as "highly desirable" but we also realise that not all organisations will be in a position, especially in early days of SDI participation, to support this approach.

If an organisation, within the context of its own business model and needs, can successfully implement WFS capabilities we would certainly encourage that. This supports more of a data transactional approach as you mention.

Lastly I would suggest we don't lose sight of the fact that there are query capabilites built into WMS. A map service may not be able to match the analytic richness offered by a feature service, but it does represent maybe a bit more than a purely cartographic option.

I'm afraid I don't have much direct control over the captchas but I'll see what I can do!

Regards, Kevin

Congratulations on making a

Congratulations on making a start on the discussion of an NZ SDI. The Cook Book contains some interesting ideas, and once there is a more useful place to engage on those ideas I will be keen to participate.

One overall comment on a theme that pervades the Book is confusion about whether the SDI should primarily (initially at least) focus on WMS or WFS. WMS is primarily a consumer (novice user level) service where as WFS is a more business focus product.

If the focus is WMS then the SDI is effectively a "map shop" service. If WFS then the SDI is a data exchange service.

I hope it is a data exchange service.

(ps your captcha is a bit daunting)

Post new comment

The content of this field is kept private and will not be shown publicly.
CAPTCHA
Please enter the words you see in the image, separated by a space

RSS feed for comments on this page