![]() You could scroll up to see any warnings that we have. And it says all 38 features are out with about seven warnings. And you can see down in the translation lock what's happening. It's just checking the source parameters, yes. The next thing we're going to do is we're just going to click run, and create the KML file. That's the open geospatial consortium, okay. You can, if you ever curious of what your reader, writers are, just go to your navigator and you could see that in the navigator it says a shapefiles, the transit routes and transit is OGCKML. So this is the KML side on the writer and the reader's shapefile. Now all four columns are green because they're going to their corresponding column on the other side, inside the KML. So I'm going to drag the little yellow arrow over to description and the shape underscore len is going to go to shape underscore length. So we have to match description, description. So just little easier to read, but look what happens, the description is now yellow and the shape link is now yellow. So I'll just double-click on that and under user attributes where you see description under user attributes, I'm just going to put the n in there and I may actually change len to length, like that. Now I may want to change the description to a proper description. And inside the writer, we've got all the KML IDs and that sort of thing, as well as the columns. And if I expand the transit routes here, you select, you can see that inside the shapefile is the FID a route, a description and shape length. So now we have transit routes going to transit routes, and I'll just zoom in a little bit. And I'm going to drag the writer over so we can see that. Now I'm just going to zoom out so we can see everything. Normally I use static schema, but for long-term projects, I use dynamic, especially when you know that field names may change within your project or the structure of the data may change just that it's dynamic, but let's leave static for now and we'll click OK. And what happens is FMI will figure out what sort of data types should be put into each category, as well as if your attributes change. Whereas the dynamic, it could be all squished together. ![]() ![]() All the attributes will be broken out into the proper type, depending on the feature type it is. You have points, that'll be its own file. So for example, if you have line work, that'll be its own file. The difference between static and dynamic is static is a one-to-one. KML, and we're going to leave static schema. Now I have an option to put KMZ or KMZ and that sort of a compressed version of KML, but by default, it'll be. And I'm just going to call this transit, transit.KML. We're going to put this directly to the desktop. We have an Esri shapefile looking at the transit route shape. If it's not in your list, again, go more formats and type K-M-L, and it should appear in the writer gallery. The format, we're going to write to is KML. We're going to leave the coordinate system alone, it'll read it from the PRJ file. These are the transit routes for the city where all the bus routes are. Now, under the desktop, under exercise files, we're in two vector data with Workbench. Next we're going to browse to the dataset. If you don't see it in your dropdown list, you can always type more formats and do a search for shp, it should appear, I'll choose it there. And the first thing I'm going to choose is as Esri shapefile. So in a brand new session, I'm going to click generate workspace. We're going to convert a shapefile into a KML format using the generate workspace inside of FME Workbench. The KML file is very useful for Google Earth or Google Maps.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |