span8
span4
span8
span4
This article provides details about three sample workspaces and their corresponding Spatial ETL tools that can help users convert topographic data to a form compatible with the Local Government Information Model and upload it to a Local Government Geodatabase.The tools and workspaces have been updated to conform to the November 5,2012 release of the Local Government Information Model.
Required Software:
ArcGIS Desktop 10.1 FME Desktop 2012 w/ SP2 or higher OR Data Interoperability Extension 2012 w/SP1 for ArcGIS Desktop
The Data Interoperability Extension for the ArcGIS Desktop can be used to view and run the Spatial ETLS tools in ArcGIS.As an alternative and if you have FME Desktop installed,you can either use it to open and run the templates in the FME Workbench or use it as an extension for ArcGIS and view and run the Spatial ETL tools in the ArcGIS environment.
Assumptions and Recommendations:
There are three workspaces attached to this article,each having a different theme.The first one covers administrative boundaries and building footprints,the second workspace focuses on road data and facilities,and the third one centers around preparing water,land cover and elevation data.To see inside a workspace,open any of the templates in FME 2012 SP2+ or open the "Topography Base Maps" Toolbox in ArcGIS and then right-click on one of the tools and choose 'Edit'.You are now in either the "FME Workbench" or the "Data Interoperability" extension of ArcGIS.
If you want to try the workspaces,all you need to do is to hit "prompt and run translation" (the play button that has a question mark next to it) and set correct parameters.You can also use them as a template to base your own solutions on.To see how the workspaces handle your data - in case you want to find out what modifications they would need to fit your purpose - there are a number of areas in them that need to be reviewed.Here,we discuss the areas shared between the three workspaces:
The workspaces attached to this article have sample data with them,but if you want to use your own data,you have to set the workspace to use your own feature types.If you are new to the FME interface,you can find information about using readers and writers inhttp://docs.亚搏在线safe.com/fme/html/FME_ReadersWriters/Content/Welcome/Welcome.htm
FME usespublished parametersto streamline user input to a workspace.The parameters can be set on runtime or when editing a workspace.In these workspaces,besides the source and destination files,you can enter a User Name and choose whether to truncate the destination tables.
Many tables in the Local Government model contain a field named "LASTEDITOR".The User Name parameter is set up in a way that if a source feature did not have an attribute that could be used to populate it's "LASTEDITOR" field in the output table,or the attribute value was blank or NULL in it,the text you enter for the User Name parameter will be written in the feature's "LASTEDITOR" field.This parameter is set up a little differently in the FME templates and the ETL tools.The difference is in leaving its value blank:
- If you are using the FME templates,FME will check for the user name with which you are logged in to the operating system you are running and use that as the user name.If it could not find the operating system's user name,it will use the word "FME" as input.
- If you are using the ETL tools with the ArcGIS Data Interoperability extension,the value will be left blank.This behavior will match the templates' behavior with upcoming Data Interoperability service packs.
The "Truncate Destination Table First" parameter determines whether you want the destination tables truncated before writing to Them.If the parameter is set to Yes,all rows will be erased from the destination tables before writing the incoming features to them.Otherwise,the new features will be appended to the tables.
You can use the AttributeRenamers provided in the workspaces to rename or create attributes and to set default values for attributes that are missing values.For more information about this transformer please refer to its description in the workbench.
Below is a screenshot of one of the AttributeRenamers used in the "Facilities and Transportation" workspace.
In the above AttributeRenamer,some attributes are being renamed (e.g.FULL_STREE to FULLNAME),some new attributes are being created (e.g.OWNEDBY,FEDROUTE),and default values are being assigned to missing attribute values (e.g.default value for OWNEDBY is set to 1)
There are two other sets of transformers used in all the three workspaces.They can work without needing any changes,but since they are used in almost all of the 亚搏在线workflows,describing them can be useful.
In most of the 亚搏在线workflows,there are pinkishbookmarksthat contain five transformers: two Testers,an AttributeCreator,a TimeStamper and a DateFormatter.Each set does the same thing.The first Tester checks if the input feature already has a value for its LASTEDITOR,if it does,then it will go straight to the second Tester,otherwise it's value will be determined by theUser Name Published Parameterand then it will be routed to the second Tester.The second one checks whether the LASTUPDATE field is populated.If it was empty,the feature is sent to a TimeStamper to populate it with your current system time and date.If a value already exists,it will go through the DateFormatter to make sure the value is formatted properly.
This bookmark is a recurring theme in the workspaces
All of the writer feature types have acustom transformernamed NullAttributeRemover right before them in the 亚搏在线workflows leading to them.This custom transformer is a slightly modified version of anFME Storecustom transformer.It checks the chosen attributes of it's input features and if an attribute has a blank value,removes it so that the geodatabase writer writes the value as NULL.
The NullAttributeRemover
In this section we go over the three workspaces in more detail.
This workspace takes input data holding information about Building footprints,Parcels,and administrative boundaries,cleans up the input and uploads it to a geodatabase.Using this workspace,features can be written to the BuildingFootPrint,OwnerParcel,LandBase,MunicipalBoundary,AdministrativeAreaBoundaryLine and County Boundary tables in a Local Government geodatabase.
The following is a screen shot of the Workspace as viewed in the FME Workbench.
Depending on your needs,you might want to add to or remove some of the transformers in the workspace.To run your data through it,in addition to thepoints mentioned in the overview section,there are a number of things to consider:
This workspace has an extra published parameter that can be set to Convert areas to miles.Four of the output tables in this workspace contain a field for area and the Local Government data model specifies the area to be in square miles.If your source data's projection uses miles as it's unit,set this parameter to none.Otherwise,set it to the appropriate value.Setting this parameter to the correct value ensures that your output area attribute is in square miles.
The area conversion parameter
The AttributeValueMapper transformer can be used to maps incoming attribute values to a needed domain and can be very helpful in mapping attributes that have relatively small domains.In this workspace,there are four AttributeValueMappers used to map output attributes that have defined domains in the Local Government Data Model.If your source attributes already follow the domains set in the Local Government model,you should remove the AttributeValueMappers from your 亚搏在线workflow.Any input attribute that is not defined in the input domain (left column),will be replaced by the default value.For more information about the AttributeValueMapper,please refer to the transformer's description.
The above AttributeValueMapper maps values to the domain of the SUBTYPEFIELD.The column in the left has
to be filled and if an input value is not in the left domain,it will be mapped to the default value (2 in here)
This workspace takes input data holding information about roads,railroads and public facilities,cleans up the input and uploads it to a geodatabase.Using this workspace,feature can be written to the RoadCenterline,Railroad,FacilitySitePoint and FacilitySite tables in a Local Government Geodatabase.
The following is a screen shot of the Workspace as viewed in the FME Workbench.
Depending on your needs,you might want to add to or remove some of the transformers in the workspace.To run your data through it,in addition to thepoints mentioned in the overview section,there are a number of things to consider:
As mentioned in more detailabove,the AttributeValueMapper is useful for mapping attributes with relatively small domains.In this workspace,the transformer is used 5 times to map some of the road attributes to their domains in the Local Government Model.
One of the AttributeValueMappers used in the workspace
Using the AttributeValueMapper to map attributes with large domains can become time consuming.Users might also already have databases or spreadsheets containing the correct attribute value mappings available.In such cases,a SchemaMapper can be used.The SchemaMapper can be a bit tricky to use,but it has several benefits.In the case of attribute value mapping,the SchemaMapper uses an external table to map attributes and unlike the AttributeValueMapper,one SchemaMapper can map more than one attribute.Although the SchemaMapper's interface has been upgraded over time,the basic logic behind it's functionality is described in great detailhereandhere.
For our purpose,I will go over one of the SchemaMappers (all SchemaMappers in this article's workspaces work the same way):
- Let's first look at how the source spreadsheet is organized.To do so,go to the folder named "Source Data-Facilities-Transportation" (delivered with the workspace template or in the ETL Tool.zip file both attached) and open the Attribute Mappings.xls excel file.
In the spreadsheet,each worksheet is used in one SchemaMapper.Let's see the one named FacilitySitePoint.
Overview of the FacilitySitePoint Worksheet in Microsoft Excel.The first row is used to identify each column in the SchemaMapper.The second row is populated with string to make the SchemaMapper treat all columns as strings
In the above example,the first column specifies the name of Input attributes.So in this case,we are handling the "SUBTYPEFIELD","OWNTYPE","FEATURECODE" and "CAPTUREMETH" attributes.The third column specifies the target attribute names.Since we have already renamed our input attributes in the workspace,the input and target attributes have the same names here.The second and fourth columns specify the attribute values in the source and target attributes respectively.The fifth column is a helper and holds code definitions taken from the Local Government Data Model.This last column is not used in the SchemaMapper.
As an example,in the above spreadsheet,we are mapping input SUBTYPEFIELD attributes that have value "COLLEGE" to output SUBTYPEFIELD attributes with value 730 (code for Education).Note that in the spreadsheet,for each input attribute name,the first line of the second column (source attribute's value) has no value.If a row for input value is left blank,it will match all inputs.So having this row on top means that 'if the attribute value on the input feature did not match with any other values specified to the same attribute in the spreadsheet,set it to whatever blank value is mapped to".Using the above spreadsheet,if an input SUBTYPEFIELD value could not be matched with the values you have set in the worksheet,it will be mapped to 790 on the output SUBTYPEFIELD attribute (to the default value in the Local Government Model).Please note that FME always uses the last match,so if you move the blank value to the last row of SUBTYPEFIELD attribute,all input values (whether they match with other rows or not) will be replaced with 790.So blank values should generally only be used on top row of each input attribute.If you completely remove the row with blank input value,then attribute values that cannot be matched will be outputted untouched.
- Now let's check the SchemaMapper transformer.In the transformer,worksheet(s) needed for attribute mapping are read and two functionalities are added: a "Filter" and a "New attribute".
The filter works on input features and in this case uses the first two columns of the Excel sheet:
The first column is used for Attribute Name Field,and the second one is set to the Attribute Value Field.Note that the two columns are Grayed The "New Attribute" creates new attributes (or replaces the existing ones) and in this case is set to use the third and fourth columns:
The third column is used for Attribute Name Field,and the fourth one for Attribute Value Field.Note that the two columns are Grayed
The three SchemaMappers used in this workspace map different attributes in RoadCenterline,FacilitySitePoint and FacilitySite tables in a local government geodatabase.To use the SchemaMappers for your own data,you need to fill in appropriate values in the second columns (Attribute code on entering Feature) of the Excel worksheets.
This workspace takes input data holding information about Water bodies,Land Cover and Elevation,cleans up the input and uploads it to a geodatabase.Using this workspace,feature can be written to the Waterline,Waterbody,Vegetation,TwentyFootContour,TenFootCountour,TwoFootContour and SpotElevation tables in a Local Government Geodatabase.If you also have source data that you want to write to the FiveFootContour table,you can either use the 亚搏在线workflow for TwoFootContour and add a FeatureTypefilter in the end of the workflow or copy the workflow and connect your source to the FiveFootContour writer feature type through the copy.
The following is a screen shot of the Workspace as viewed in the FME Workbench.
Depending on your needs,you might want to add to or remove some of the transformers in the workspace.To run your data through it,in addition to thepoints mentioned in the overview section,there are a number of things to consider:
This workspace uses two SchemaMappers to map input attributes to the domains of the "TYPE" attributes in the Waterline and Waterbody tables of a Local Government geodatabase.Detailed information about the way the Excel worksheets are organized and used in SchemaMappers can be foundabove.
As the transformer's name implies,it calculates input polygons' areas.This transformer is only used once in the workspace,so no area conversion parameter was published for it.If your source data's projection uses a unit other than Miles,you can enter a conversion rate in the AreaCalculator's Multiplier parameter.
The multiplier is set to convert square feet to square miles
These workspace are intended to provide you a starting point and assist you in loading your data into an existing Local Government file geodatabase using best practices.
It is expected that you may have different source formats and schemas and you may need to tweak this workspace to work with your own data.
If you have issues or questions related to this workspace please contact us atfme.ly/supportand title the subject as "ArcGIS Local Government Topography Basemaps" so it is quickly directed to the best resource here at 亚搏在线Safe Software Support.
Reading Basic Geodatabase Annotation - GDB to DWG
Performing spatial queries on database tables using the FeatureReader
Reading Basic Geodatabase Annotation - GDB to DGN
How do I convert curved text from Geodatabase to Microstation DGN?
Election Results for Local Government
Geodatabase Behaviour: Updating a File Geodatabase
Using FME to load images into Geodatabase attachments
Using the FeatureReader to Query a Geodatabase
Writing Geodatabase Relationship Classes
Comparison of FME readers and writers for SDE and Geodatabase
© 2019 亚搏在线Safe Software Inc |Legal