I have an existing process that processes versioned views from an ESRI SQL Server Geodatabase to another SQL Server Database creating SQL Spatial tables with a geometry column that I have reprojected to WGS84 Lat Long. Can I add a second geometry field to the SQL spatial tables and populate that column with Web Mercator geometry? I am trying to figure out a single workflow that would calculate both columns in the same table. Or am I restricted to calculating one geometry column at a time in separate processes?
Question
Multiple Geometry in SQL Spatial Table
+17- Safer
Hi
Thank you for posting your question on the FME Community! You should be able to populate both geometry columns in a single FME workspace. You can find a helpful reference here that explains how FME handles tables with more than one geometry column:
FME isn’t yet able to create tables with multiple geometry columns. You may either use an existing table with multiple geometry columns, or you can use a SQL script within the FME translation to create one.
FME can preserve the SRID for multiple geometry columns, but this requires some setup. For each geometry, you’ll need to set the geometry trait “Coordsys” with the coordinate system (which can be determined using the CoordinateSystemExtractor). For each geometry:
- Use a CoordinateSystemExtractor to determine the coordinate system and set the attribute “Coordsys”.
- Use a GeometryPropertySetter, set to Traits from Attributes, and select the Coordsys attribute.
- Aggregate the geometries and use the MultipleGeometrySetter.
Hope this information helps!