geojson file using the naming convention SourceGeoJSONFile_GeometryType. A separate feature class will be created for each geometry type in the input. The GeoJSON specification supports multiple geometry types. See Schema.ini File (Text File Driver) in the Microsoft documentation for more information.įor input Excel worksheets and tabular text files, only point geometry is supported. To use an input table with a nonstandard delimiter, the delimiter must be specified using a schema.ini file. txt extensions is a comma for files with a. The standard delimiter for tabular text files with. A valid latitude and longitude location is required in the source KML. Point locations that use the address tab (by way of geocoding) are not supported. KML and KMZ input up to KMZ version 2.2 of the Open Geospatial Consortium KML standard is generally supported. sde) is specified as a UNC path in the Target Geodatabase parameter and that the path is accessible by the enterprise geodatabase. If you are importing files into an enterprise geodatabase, ensure that the database connection file (. For example, if the Target Geodatabase value is C:\Data\OperationalData.gdb, a folder named OperationalData_Rasters will be created under C:\Data. ![]() These files are named after the Target Geodatabase value and appended with _Rasters. This is located at the same location as the target geodatabase. The source rasters referenced by the mosaic dataset are stored in their native format in a subfolder named after the mosaic dataset. kmz file, are converted into a mosaic dataset in the Target Geodatabase parameter. ![]() Rasters, or ground overlays contained in a. ![]() The Filter parameter can be used to limit which files are imported from folders. The Input Data value is a folder, it will be recursively searched for KML (.
0 Comments
Leave a Reply. |