Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
To achieve true data interoperability is to eliminate format and data model barriers, allowing you to seamlessly access, convert, and model any data, independent of format. The ArcGIS Data Interoperability extension is based on the powerful data transformation capabilities of the Feature Manipulation Engine (FME), giving you the data you want, when and where you want it.In this course, you will learn how to leverage the ArcGIS Data Interoperability extension within ArcCatalog and ArcMap, enabling you to directly read, translate, and transform spatial data according to your independent needs. In addition to components that allow you to work openly with a multitude of formats, the extension also provides a complex data model solution with a level of control that would otherwise require custom software.After completing this course, you will be able to:Recognize when you need to use the Data Interoperability tool to view or edit your data.Choose and apply the correct method of reading data with the Data Interoperability tool in ArcCatalog and ArcMap.Choose the correct Data Interoperability tool and be able to use it to convert your data between formats.Edit a data model, or schema, using the Spatial ETL tool.Perform any desired transformations on your data's attributes and geometry using the Spatial ETL tool.Verify your data transformations before, after, and during a translation by inspecting your data.Apply best practices when creating a workflow using the Data Interoperability extension.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Der Datensatz liefert die Geokoordinaten der Hausnummern in Bonn mit Angabe des Gemeindeschlüssels, Verwaltungsheinheit, Gemeindename, Ortsteil, Straßen-Schlüssel und Straßennamen.Quelle: OFFENE DATEN: BONNVerarbeitungsprozesse: JSON Datei wurde mit FME und ArcGIS Pro konvertiert und als Feature Service in ArcGIS Online veröffentlicht.
Title 36, Code of Federal Regulations, Chapter II, Subpart B, may close an area to entry or may restrict the use of an area by applying any or all of the prohibitions authorized by the code of regulations. These prohibitions, usually referred to as a forest order, are required to be displayed in [a] manner as to reasonably bring the prohibition to the attention of the public.Official documentation on this code and its subparts can be found here: https://www.gpo.gov/fdsys/pkg/CFR-2011-title36-vol2/pdf/CFR-2011-title36-vol2-sec261-50.pdfThis feature class was created from a joint request from Office of Communications and Fire & Aviation Management at the forest level to allow for an interactive map display of forest orders to the public. In order to maintain consistency across the region, a workflow has been established to facilitate the display of forest orders to the public. Each forest will maintain a forest order feature class. Through FME workbench, a regional forest order feature class will be updated daily from the Forests’ feature classes via FME scheduler. The regional feature class is driven by the dates in the Forests’ feature classes, which allows for historical collection of forest orders. The FME workbench also creates and publishes to ArcGIS Online a region-wide forest order map service from the regional feature class. This map service is displayed in an individually created web map that each forest can embed on their public facing website.
Data provided by Metropolitan Atlanta Rapid Transit Authority (MARTA) General Transit Feed Specification (GTFS) at https://www.itsmarta.com/app-developer-resources.aspxCity of Sandy Springs translates the stops, shapes, routes and trip files in FME with FME Workbench. The Stops and Routes are published to ArcGIS online. General Transit Feed SpecificationThe MARTA GTFS feed is updated approximately four times per year, which is about how often MARTA service changes. It will be published to the same URL with each new update.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Standorte mit Bezeichnung der öffentlichen Fahrradstellplätze im Bonner Stadtgebiet.Quelle: OFFENE DATEN: BONNVerarbeitungsprozesse: JSON Datei wurde mit FME und ArcGIS Pro konvertiert, nach WebMercator projiziert und als Feature Service in ArcGIS Online veröffentlicht.
Sewer Nodes has been compiled from a number of TasWater supplied datasets (south, north and north-west regions). Datasets converted, merged and reprojected (where necessary) into GDA using Feature …Show full descriptionSewer Nodes has been compiled from a number of TasWater supplied datasets (south, north and north-west regions). Datasets converted, merged and reprojected (where necessary) into GDA using Feature Manipulation Engine (FME) before being stored in an ESRI ArcSDE environment.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Bridges, Buildings, and Street Pavement area as derived from lidar data in 2013 and digitized from aerial photography with ad hoc updates. The field “Layer” delineates if the record is a bridge, building, or road. This is typically used as a cartographic layer and not an impervious surface assessment; however, it may be useful as a proxy measure for built-upon area estimations. For example, areas with more buildings and pavement will probably have more impervious surface, but this layer does not account for private parking lots, swimming pools, or other impervious features. Data is updated by an automated process using FME. Note to administrators, do not rename or move this feature service without updating underlying FME process.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Der Datensatz liefert den mittlerer Lärmpegel des ganzen Jahres (Stand 2012). Der resultierenden Lärmpegel wird in dB(A) angegeben.Quelle: OFFENE DATEN: BONNVerarbeitungsprozesse: JSON Datei wurde mit FME und ArcGIS Pro konvertiert, nach WebMercator projiziert und als Feature Service in ArcGIS Online veröffentlicht.
This shapefile contains the green area of a small portion of the UJI campus extracted using FME extraction tools to extract the green area from a drone image.
Data provided by Metropolitan Atlanta Rapid Transit Authority (MARTA) General Transit Feed Specification (GTFS) at https://www.itsmarta.com/app-developer-resources.aspxCity of Sandy Springs translates the stops, shapes, routes and trip files in FME with FME Workbench. The Stops and Routes are published to ArcGIS online. General Transit Feed SpecificationThe MARTA GTFS feed is updated approximately four times per year, which is about how often MARTA service changes. It will be published to the same URL with each new update.
Der Landkreis Cham betreibt im öffentlich Bürgerservice bereits seit Jahren ein WebPortal auf Basis von ArcGIS Online mit einem hybriden Ansatz (Datenhaltung On-Premises). 2021 wurde nun auch die interne GIS-Nutzung in einem geschlossenen kommunalen Behördennetz auf dieselbe Technologie auf Basis von ArcGIS Enterprise umgestellt (komplett On-Premises). Hierbei eröffneten sich auch für die „Normalanwender“ enorme 3D-Möglichkeiten, die zuvor nur den „Power-Usern“ mit Desktop-GIS vorbehalten waren. Eine der Grundvoraussetzungen hierfür ist die performante und einfache Nutzung von 3D-Szenen-Daten und -Diensten in Webbrowsern. Das i3s-Format (unter ArcGIS SLPK) hat sich hier als sehr gut geeignet erwiesen. Die Ableitung solcher Datensätze bedingt aber zum einen eine hohe fachliche Qualifikation der Administratoren. Zum anderen werden FME-Technologien, beispielsweise über ArcGIS Data Interoperability for Desktop, benötigt. Über beides verfügen leider nicht viele Landkreise. Von dem kommenden OGC-Standard 3D Portrayal Service und der Beteiligung an dem Projekt der RT GIS e.V. versprechen wir uns hier eine grundsätzliche Abhilfe. Neben LoD2-Daten wurden von uns landkreisweit auch DGM1-, DOP20- und DOM40- und testweise auch DOM20-Daten (nur Stadt Cham) eingebunden. Hier ein Beispiel (Stadtplatz Furth im Wald)
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Der Datensatz liefert die Standorte der Parkhäuser in Bonn. Für die Parkhäuser der City Parkraum GmbH stehen auch die aktuellen Belegdaten als API zur Verfügung.Quelle: OFFENE DATEN: BONNVerarbeitungsprozesse: JSON Datei wurde mit FME und ArcGIS Pro konvertiert, nach WebMercator projiziert und als Feature Service in ArcGIS Online veröffentlicht.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Standorte mit Bezeichnung der öffentlichen Parkplätze (PKW-, Motorrad-, Wohnmobil/Wohnwagen- und Busparkplätze) im Bonner Stadtgebiet.Quelle: OFFENE DATEN: BONNVerarbeitungsprozesse: JSON Datei wurde mit FME und ArcGIS Pro konvertiert, nach WebMercator projiziert und als Feature Service in ArcGIS Online veröffentlicht.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
R4 Forest Order ArcGIS Server map service layer registered in ArcGIS Online.A Forest Order is a polygon that represents the area of a prohibition. A prohibition that is a line or point feature, such as a road closed to motor vehicle use, will be represented by a buffer of the line or point feature to create a polygon. The forest order feature class contains existing and/or future forest orders on National Forest System lands in the Intermountain Region (Region 4). This dataset is in development and may not represent all prohibition. The Alerts & Notices link at https://www.fs.usda/gov/r4 as well as the individual forest sites should be examine for the most current information. Title 36, Code of Federal Regulations, Chapter II, Subpart B, may close an area to entry or may restrict the use of an area by applying any or all of the prohibitions authorized by the code of regulations. These prohibitions, usually referred to as a forest order, are required to be displayed in [a] manner as to reasonably bring the prohibition to the attention of the public. Official documentation on this code and its subparts can be found here. In order to maintain consistency across the region, a workflow has been adopted to facilitate the generation of forest order data. Each forest will maintain a forest order feature class. Through FME workbench, a regional forest order feature class will be updated daily from the forests feature classes via FME scheduler. The regional feature class is driven by the dates in the forests feature classes, which allows for collection of forest orders. Full metadata can be found at here.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Flächen aller städtischer Liegenschaften (Grundstücke der Stadt Bonn) im Bonner Stadtgebiet mit Ausnahme von Pachtgrundstücken.Quelle: OFFENE DATEN: BONNVerarbeitungsprozesse: JSON Datei wurde mit FME und ArcGIS Pro konvertiert, nach WebMercator projiziert und als Feature Service in ArcGIS Online veröffentlicht.
Updates every Friday via FME. FME updates this layer and the hosted public-view CIP layers.Any edits to the Shared Use Path locations should be done in SDE.
PCC 3Waters Asset Data exported from the Master Database at Wellington Water Ltd. It is made up of 19 layers. Please check the date for the latest Data Updated date.Height levels are in terms of NZVD2016 as of 1 July 2022.*This Federated Feature Service references our data in an Enterprise geodatabase (egdb) which is updated daily via FME workbench from InfoAsset. It has limited symbology and includes Abandoned, removed & virtual assets. It's purpose is so that staff can access the raw data which is updated daily. They can add it to their Arc Pro projects and it allows them to view the attribute tables & change symbols. It's other purpose is so that councils and the public can download the data form our Open Data Portal. It is only shared with our organisation in Enterprise because we dont want the public to use it as it is hosted on "our" server which is not as robust as the ESRI server. Also, if it's shared with the public, it may slow down the service for our staff. So every week it is copied to AGOL as a Hosted Feature Service which is shared with the public and our Open Data Portal.
SWDC 3Waters Asset Data exported out of Master database daily at Wellington Water Ltd (WWL). Height levels are in terms of NZVD2016 as of 1 July 2022.*This Federated Feature Service references our data in an Enterprise geodatabase (egdb) which is updated daily via FME workbench from InfoAsset. It has limited symbology and includes Abandoned, removed & virtual assets. It's purpose is so that staff can access the raw data which is updated daily. They can add it to their Ar Pro projects and it allows them to view the attribute tables & change symbols. It's other purpose is so that councils and the public can download the data form our Open Data Portal. It is only shared with our organisation in Enterprise because we dont want the public to use it as it is hosted on "our" server which is not as robust as the ESRI server. Also, if it's shared with the public, it may slow down the service for our staff. So every week it is copied to AGOL as a Hosted Feature Service which is shared with the public and our Open Data Portal.
SWDC 3Waters Asset Data exported out of Master database daily at Wellington Water Ltd (WWL). Height levels are in terms of NZVD2016 as of 1 July 2022.*This Federated Feature Service references our data in an Enterprise geodatabase (egdb) which is updated daily via FME workbench from InfoAsset. It has limited symbology and includes Abandoned, removed & virtual assets. It's purpose is so that staff can access the raw data which is updated daily. They can add it to their Ar Pro projects and it allows them to view the attribute tables & change symbols. It's other purpose is so that councils and the public can download the data form our Open Data Portal. It is only shared with our organisation in Enterprise because we dont want the public to use it as it is hosted on "our" server which is not as robust as the ESRI server. Also, if it's shared with the public, it may slow down the service for our staff. So every week it is copied to AGOL as a Hosted Feature Service which is shared with the public and our Open Data Portal.
Amtrak train locations are updated every 15 minutes in this dataset via an automation in FME Flow. FME uses an HTTP Caller to extract JSON data from api-v3.amtraker.com, an API made and updated by piemadd on GitHub. The GitHub library and its creator have no relation to Amtrak. Once the JSON data is pulled in to FME, it is flattened and formatted so individual train locations can be mapped via provided coordinates. Users can compare this feature layer to the Track Your Train Map hosted by Amtrak; the original intent of this layer was to provide the Amtrak train location data in a useable GIS format rather than an app that cannot be expanded upon with extra detail or functionality.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
To achieve true data interoperability is to eliminate format and data model barriers, allowing you to seamlessly access, convert, and model any data, independent of format. The ArcGIS Data Interoperability extension is based on the powerful data transformation capabilities of the Feature Manipulation Engine (FME), giving you the data you want, when and where you want it.In this course, you will learn how to leverage the ArcGIS Data Interoperability extension within ArcCatalog and ArcMap, enabling you to directly read, translate, and transform spatial data according to your independent needs. In addition to components that allow you to work openly with a multitude of formats, the extension also provides a complex data model solution with a level of control that would otherwise require custom software.After completing this course, you will be able to:Recognize when you need to use the Data Interoperability tool to view or edit your data.Choose and apply the correct method of reading data with the Data Interoperability tool in ArcCatalog and ArcMap.Choose the correct Data Interoperability tool and be able to use it to convert your data between formats.Edit a data model, or schema, using the Spatial ETL tool.Perform any desired transformations on your data's attributes and geometry using the Spatial ETL tool.Verify your data transformations before, after, and during a translation by inspecting your data.Apply best practices when creating a workflow using the Data Interoperability extension.