Here’s a reminder for you to pop out and buy a card to congratulate Don and Dale on the arrival of their new offspring: FME2010. As always, the parents are very proud - though slightly exhausted - and confident this new born will be a hit with all. In fact, I’m so smitten I’ve created a top-ten list of my favourite things about the new release.
Once upon a time, a geo-nerd converted spatial data into a 3D model. He (or she) wanted to record coordinate transformation parameters so the data could get home again. A trail of breadcrumbs didn’t work, nor did a WLD file. So a fairy godmother from Safe Software waved a magic wand, and….
This short post is about what to do when FME doesn’t recognize your coordinate system - and highlights a very little known transformer: the CoordinateSystemDescriptionConverter.
This post is on the subject of city models and how to bring together CAD, GIS, BIM, DEM, raster and other types of spatial data to create a single model. This example includes 3D buildings, DEM draping, rasterization, reprojection, and writing out to PDF - and all in just 13 transformers!
Oh what a tangled web you weave, when first you practice to use the SchemaMapper. Hopefully this post will unpick some of the more tangled issues when you dive into mapping Feature Types and Attributes with multiple where clauses from the same lookup tables, or when using it to set attribute values like a dynamic ValueMapper transformer.