span8
span4
span8
span4
This article has been depreciated,for current information on working with FME and REST,see theFME Server REST API Training course.
RPC web services are easier to create than REST web services,because they rely on a very small portion of the HTTP standard.In another section we'll go through how to deal with the HTTP standard,but let's start with what is common between REST and RPC web services created with FME Server.Whether it's REST or RPC,it all starts with a workspace.Once the workspace is authored it is then published to FME Server to create a web service.
In this section we will create a RPC web service that will be the basis of a REST web service we create later.
The first we want the web service to provide all of the parks in GeoJSON format.
Use the Service
This service can now be used by an app to get the spatial and attribute information for all parks.
Retrieving all the parks is a good start,but it's possible that an app will only want information on certain types of parks.In this case we need to allow an option to be specified on the URL;an HTTP parameter.FME Server translates HTTP parameters into published parameters,which are options understood by a FME workspace.
This service can now be used by an app to get the spatial and attribute information for all parks,those with dog parks or those without.
Creating REST Web Services.zip
Tutorial: Working with List Attributes
Transformers for Working with List Attibutes
Build Records from Name - Value Lists
Computing a Histogram on a List
Template: Convert KML name/value pairs from a list to new attributes
Eliminate unused attributes from a source schema
CAD to GIS: Convert Parcel Lines and Text from DGN to Geodatabase
Testing with If-Then Conditional Statements
© 2019 亚搏在线Safe Software Inc |Legal