Home › Blog Archives ›

March 2012

Exploring the PIM: Versions and Users
Wednesday, March 28, 2012

This post will begin to introduce PIM and PIM API organization.  The PIM API is coupled with the tables and views in the PIM based on the rule set discussed in the previous post.

The fundamental object (and table) in the PIM API and the PIM is the pimVersion.  Each element in the PIM and PIM API is tied to a version.  In the current structure, pimVersions are identified (pimVersion.ID) by a real number.  The use of a real number in this context as opposed to some string value; e.g. '2.1.4', is arbitrary and can be easily accommodated in small PIM revisions. 

read more

Understanding Geospatial Data Rules in the Platform Independent Model (PIM)
Saturday, March 24, 2012

This post continues a series describing our approach to using a platform-independent approach to managing data models and standards. In any situation where a geospatial data model is agreed upon and adopted by multiple participants, management of the model itself becomes a significant issue. Over time, modifications to the model are required. Such modification can have significant impacts on the implementations of each participant. As a result, configuration management is needed to ensure smooth transition and traceability between data model versions.

read more

Applying Flexible, Yet Standard, Geospatial Conventions
Monday, March 19, 2012

Previous posts have touched the problems that traditionally face those wanting some geospatial consistency in data collection, data presentation, and data understanding.  These issues drive much of the continual interest and push for increased Metadata and many of the "Use Liability" clauses that are attached to current datasets.  After all, if you don't really know what the feature is, or what many of the attributes really mean, geospatial data is of considerably reduced value.

read more