Hi Brandon,

there are some transformers in FME like the intersector and some custom
transformers on fmepedia like the sliverpolygonremover
http://www.fmepedia.com/index.php/Overlap-Sliver_Removal_Workspace

But we have found out that there is no garantee that SDE will accepts the
data coming out of FME due to the coordinate shiftings you can encounter
with the GDB Coordinate Precision.

What we usually do is this:

Load data into a personal geodatabase.
Repair the geometries with PYTHON.
Load the data with FME.

Encapsulate all this in a batch script, a geoprocessing model or another
application.

So the first thing would be to write a geoprocessing script with Python to
repair geometries.
Have a look at this sample:
http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=Checking_and_repairing_geometries

Afterwards you can call fme to load them.

In a dos batch file it would be something like this :

for %%f in (*.mdb) do (
python.exe "yourpythonscript.py" "your arguments"
fme.exe "yourworkbenchfile.fmw" "your options"
)

Greetings from Switzerland,
Jeff Konnen
GIS Analyst
INSER SA

On 4/3/07, bjwotaski <[EMAIL PROTECTED]> wrote:

  HI:

I am working on an ETL project in which parcel datasets (polygons)
are being taken from a number of counties and ingested into an
ArcSDE spatial database. We want the process to be as automated as
possible. Here is how we would like it to go: parcel data from the
counties is placed on an ftp site, then at a certain time, the data
is downloaded from the ftp site to a folder on either a computer or
server, then the data is manipulated in FME Workbench to extract the
necessary attribution and then dumped into our ArcSDE spatial
database. Once all the counties data has been initially downloaded
and put into SDE, periodically we would want the process to run, to
check for updates to the parcel data, i.e., new parcels, change of
attribution.

I have been able to successfully ETL two counties data into SDE
using FME Workbench. The problem I have run into with other
datasets is the fact that the dataset (shapefile and personal
geodatabase feature classes) have polygons with bad geometry that
Workbench does not like. I have been able to fix the geometry
problems using ArcGIS—ArcToolbox--Repair Geometry. Is their a
function in FME Workbench that will do the same thing, essentially
fixing polygons with bad geometry, such as sliver, self
intersections, and short segments?

If not, does anyone know if it is possible and how it can be done,
to do the following: once the files are ftp'd from the county, tell
ArcToolbox to check the geometry and repair if necessary and then
have FME Workbench startup and perform the ETL on the dataset and
load the finished data into SDE? Each county would have an .fmw
already created for each county, based on the initial dataset we
get. The transformers I am using in Workbench are pretty straight
forward, mostly copying and creating attributes. I am not much of a
programmer and know very little about scripts and programming
language, so I am not sure how this could be done, any help or
advice anyone would have would be greatly appreciated.

Thanks much,

Brandon






--
Jeff Konnen
INSER SA
Switzerland
+41 (0) 21 643 77 11

Reply via email to