Jeffery J. Jensen, PE
Adjunct Professor

University of Nevada Las Vegas
Department of Civil and Environmental Engineering
4505 S Maryland Pkwy
Box 454015
Las Vegas NV 89154-4015

Email: jefferyjjensen@gmail.com
Mobile: 702-327-9294
Jeff Jensen Notes Safe Software FME

Safe Software's FME

FME Training

  1. download training manual from http://cdn.safe.com/training/course-materials/Training-Workbook-Exercises.pdf
  2. download the training pack from http://cdn.safe.com/training/course-materials/FME_Training_Self_Study_Pack_v2012.zip
  3. download training data from http://cdn.safe.com/training/tutorials/FME-Sample-Dataset-Full.zip

FME Support

FME Workbench

Documenting FME Workbench

FME Server

FME Universal Viewer

Background on FME and Google Earth KML files

Using FME to create static KML/KMZ files for Google Earth and Map

  1. Creating KML Features
  2. Symbolizing and Labeling KML Features
  3. Display KML Attributes
  4. Edit KML Features
  5. Using FME to convert TBC to KML
  6. FME Extras

FME Coordinate Transformations


FME and ESRI World File - Grid to Ground


FME Shapefile Transformation - Grid to Ground


ArcGIS, FME and Google Earth


Steps to create a KML/KMZ using FME Workbench


Projections - Stateplane to Lat/Long

Using KML Network Links and Regions


Random Color Generator using FME KMLStyler Transformer


Adding a Company Logo as a Screen Overlay


How to Label Features in a KML file


How to Symbolize KML file


The FME KMLStyler


Descriptor Balloon


KML Extended Data and Hyperlinks

Create Hyperlinks within a KML Balloon Descriptor


KML Folders - How to group features


KML Document Name


Merge KML Files

Merge several kml/kmz files into a single KMZ using Google Earth


Merge several kml/kmz files into a single KMZ using FME Workbench

Using FME to convert TBC to KML


element cannot contain any <Document> elements.
FME KML Writer
KML Element Attribute KML Element FME Description
kml_document <Document> <Document> element is a container element for <Folder>, <Placemark>, <GroundOverlay>, <ScreenOverlay>, <PhotoOverlay> and <NetworkLink>. KML has two container element types: <Folder> and <Document>, which in many ways are functionally equivalent. For practical purposes, the KML writer assumes that each KML file has a single <Document> root element, which cannot contain subsequent <Document> elements. Furthermore, the KML writer also assumes that each <Folder>
Common element attributes to all fixed schema feature types with exception of Style and StyleMap
kml_id @id
kml_name <name>
kml_visibility <visibility>
kml_open <open>
kml_address <address>
kml_phone_number <phoneNumber>
kml_snippet <Snippet> element value written without xml entity encoding
kml_description <description>
kml_description_text <description> completely overrides any text provided by FME
kml_description_raw_text <description> Element value written without xml entity encoding
kml_style_url <styleUrl>
kml_atom_author_name <atom:author>
kml_atom_author_email <atom:email>
kml_atom_link_href <atom:link href-"@">
kml_atom_link_rel <atom:link rel="@">
LookAt - defines a simpler virtual camera for viewing features
KML Element Attribute KML Element FME Description
kml_lookat_heading <LookAt><heading>
kml_lookat_tilt <LookAt><tilt>
kml_lookat_altitude <LookAt><altitude>
kml_lookat_range <LookAt><range>
kml_lookat_latitude <LookAt><latitude>
kml_lookat_longitude <LookAt><longitude>
Region elements can be added to any feature, and describe an area of interest defined by a bounding box, and either a altitude or a specified Level of Detail (LoD) extent. (see FME Readers and Writers)
KML Element Attribute KML Element FME Description
kml_latlonaltbox_altitude_mode <LatLonAltBox><altitudeMode>
kml_latlonaltbox_min_altitude <LatLonAltBox><minAltitude>
kml_latlonaltbox_max_altitude <LatLonAltBox><maxAltitude>
kml_latlonaltbox_north <LatLonAltBox><north>
kml_latlonaltbox_south <LatLonAltBox><south>
kml_latlonaltbox_east <LatLonAltBox><east>
kml_latlonaltbox_west <LatLonAltBox><west>
kml_lod_min_lod_pixels <Lod><minLodPixels>
kml_lod_max_lod_pixels <Lod><maxLodPixels>
kml_lod_min_fade_extent <Lod><minFadeExtent>
kml_lod_max_fade_extent <Lod><maxFadeExtent>
Placemark elements contain vector geometry that is displayed within Google Earth. (see FME Readers and Writers)
KML Format Attribute KML Element FME Description
kml_common_style unique string which identifies the common style
kml_icon either a name of an icon or path to an icon
kml_create_info_point forces the creation of an aggregate point containing the original feature geometry and a point. Used for creating Placemarks that are clickable but styled using an external style element
kml_target_style
kml_target_style_normal Contains the id of an associated style element that should be active when the placemark is not active. If specified kml_target_style_highlight must also be specified. Will result in the creation of the appropriate StyleMap element
kml_target_style_highlight contains the id of an associated style element that should be active when the placemark is highlighted on mouse-over. If the specified kml_target_style_normal must also be specified. Will result in the creation of the appropriate StyleMap element
GroundOverlay. (see FME Readers and Writers)
LatLonBox - Specifies where the top, bottom, right, and left sides of a bounding box for the ground overlay are aligned. Not required for writing rasters that are appropriately georeferenced. A <GroundOverlay> element must contain a <LatLonBox> element that defines the bounding box of the overlay. If the ground overlayu feature has a raster geometry, these FME attributes will be automatically populated using the feature's bounding box.
FME KML Element Attribute KML Element FME Description
kml_latlonbox_north <LatLonBox><north>    
kml_latlonbox_south <LatLonBox><south>    
kml_latlonbox_west <LatLonBox><west>    
kml_latlonbox_east <LatLonBox><east>    
kml_latlonbox_rotation <LatLonBox><rotation>    

FME and SQL Server

Options to load GIS data into SQL Server

Licensing

How to Connect FME to Microsoft SQL Server installed on Godaddy ISP

SQL Server 2008 Spatial


FME and MySQL

MySQL Background

How to Connect Autodesk Civil 3D to MySQL spatial database

MySQL Load Data Infile

MySQL Command Line Tool and Scripts

MySQL GUI Tools

MySQL Comments

MySQL Databases

MySQL Create and Drop Tables

MySQL variables

MySQL on bluehost issues

How to Export MySQL database

Connecting to MySQL installed on Bluehost ISP

Google and Bluehost Notes

MySQL Query Browser - MySQL GUI Tools

How to import CSV files into MySQL using FME Workbench

MySQL Questions


FME and AutoCAD DWG

FME Geocoding

FME Geocoding with Google Maps API

  1. http://maps.googleapis.com/maps/api/geocode/xml?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&sensor=false
  2. Add a Creator Transformer
  3. User Parameters → Published Parameters → right click Add Parameter
  4. Add an AttributeCreator Transformer
  5. Add a StringConcatenator Transformer
  6. Reading Complex XML or GML using the XMLFlattener

FME Geocoding with Gisgraphy

  1. Create a .csv file with addresses you want to geocode such as geocodeaddresses.csv
  2. Download FME Workbench example Geocoding with FME Using Gisgraphy and open in FME Workbench (can just double click the *.fmw file)
  3. Readers → Add Reader
  4. Connect the reader to the StringConcatenator
  5. Modify the StringConcatenator
  6. Delete "Parameters to make an address Record" bookmark with the Creator and AttributeCreator transformers
  7. Add KML Writer
  8. Delete the MapInfo writer
  9. Run the workspace

FME Batch Deploy


FME Shapefile Transformation - Grid to Ground

[an error occurred while processing this directive] Engineering College of UNLV