The Basics of hale»studio

In the past years, we’ve been asked by many customers to review their hale transformation projects. Sometimes users just want to get an opinion on a specific problem they encountered, but often, the scope was wider. Users are concerned at whether the projects they create will result in valid output. We’ve thus now developed a “certification” process for transformation projects. In that process, we check for a wide range of potential issues: General ChecksAre there any performance issues? Was the source data mapped as far as possible? Were all required types in the target model created? Are there obvious semantic inconsistencies or mismatches? Are there any validation warnings? Does the execution generate any errors or warnings? How well are edge cases handled, such as invalid data or data variants? Is there sufficient documentation on the alignment and on the used data sources? Do all filters/contexts work as intended? When using Groovy Script functions or Custom Functions, are these correct? Do they pose a security risk? Read More

If you have been creating INSPIRE GML, you have almost certainly encountered so-called codelists. They are an important part of INSPIRE data specifications and contribute substantially to interoperability. They are, however, not as straightforward as a simple enumeration is. This post explains what codelists are, how you use… Read More

Many people who create GML, and in particular INSPIRE GML, hit some common challenges around identifying features. In part, these come from technical requirements of XML/GML, and in part they come from INSPIRE requirements. An INSPIRE feature will generally have three properties that identify objects, each with a different… Read More