|
IDEA
|
Hi, I know of people who have written one but not productized, Simon Jackson do you know any?
... View more
08-28-2019
07:20 AM
|
0
|
0
|
3661
|
|
IDEA
|
Hi You can publish a feature service from data in S3 with Koop. Alternatively, the Data Interoperability extension can upload and download data from S3.
... View more
08-27-2019
01:43 PM
|
1
|
1
|
3661
|
|
IDEA
|
Hello, you should be able to do this with the cx_oracle package. May I ask if the data needs to be geocoded to find XY values?
... View more
08-26-2019
02:41 PM
|
0
|
0
|
583
|
|
POST
|
To everyone on this thread, we have looked into the original issue and found the cause, we are planning a patch for Data Interoperability for the week September 3-6 (September 2 is a holiday), we apologize for the inconvenience.
... View more
08-20-2019
08:53 AM
|
1
|
1
|
3902
|
|
POST
|
Hi, Data Interoperability extension can read Lizardtech MrSID. The workflow would be to convert the data to a supported raster dataset.
... View more
08-20-2019
08:44 AM
|
0
|
2
|
14258
|
|
POST
|
Hi, try this: https://pm.maps.arcgis.com/home/item.html?id=d887241f6908466a984c94631fd1974f Regards
... View more
08-14-2019
12:18 PM
|
1
|
2
|
1594
|
|
BLOG
|
Everyone likes SQLite. It is a single portable file, performs and scales well, supports enough SQL to be useful and has a DB-API compliant Python module and API access in other languages. It is embedded in many mobile and desktop apps, and is directly usable in ArcGIS Pro. SQLite as a container has an incarnation - OGC GeoPackage - that supports the encoding of vector and raster features for direct use in ArcGIS Pro. You can read about the standard on the OGC website. The GIS format most often compared with GeoPackage is the Esri-defined shapefile. Shapefile is the most shared GIS format on the planet and its encoding of vector features is published. Note however the publication date - 1998. At the time the shapefile was designed, the components available had limitations that can frustrate today's advanced workflows. These include file size limit, attribute field count and name width limits, dates not supporting time, complexity in handling character encodings and lack of null value support for most field types. Shapefile has been spectacularly successful for handling simple vector features, but it can be limiting. I think of GeoPackage as the new shapefile without the old limitations and I encourage you to use it. It is a great format for, well, geo-packaging! However, don't go as far as thinking it is a full-blown GIS workspace, it doesn't have geodatabase behaviors like domains and attribute rules. What it does, it does well. GeoPackage is extensible, and there are approved OGC extensions for gridded tiles of elevation data and table relationships, and non-approved community extensions such as map styling of features and storing vector tiles. ArcGIS Pro does not yet implement support for any GeoPackage extensions (excepting table functionality adopted in the v1.2 release). What can you do with a GeoPackage in ArcGIS Pro 2.6? Read and write simple features (polygons, polylines, points, multipoints, circular arcs, tables) Create feature classes with the Feature Class to Feature Class tool Create tables with the Table to Table tool Use Copy/Paste in the Catalog pane Use the Append tool to add data to an existing feature class or table Use the Add Raster To Geopackage tool to store imagery Edit features or rows with the ability to undo and redo edits Modify the schema Geoprocess with any tool that takes a simple feature class or table as input Share GeoPackage data with other users as a static item in ArcGIS Online Use Geopackage vector and raster data in map workflows Read or write GeoPackage in Data Interoperability ETL workflows Use SQL statements in SQLite's native dialect What can you not do with a GeoPackage in ArcGIS Pro 2.6? Publish a GeoPackage item as a hosted web layer Store or edit metadata Use any geoprocessing tool that requires geodatabase output Some recommendations: You can add fields and calculate values with geoprocessing tools or ArcPy, but you may find it slower than native geodatabase operations. Geometry storage in a GeoPackage is not compressed like a geodatabase, so they can get big. Do your geoprocessing before creating your GeoPackage, then copy your data into it. Think of GeoPackage as a sharing format. Move your data into the GeoPackage like this: Create a GeoPackage with the Create SQLite Database tool (using the GeoPackage spatial type) Use the Copy tool (Data Management, General toolset) to add vector data, or Copy/Paste in the Catalog pane Use the Add Raster to GeoPackage tool (Conversion, To GeoPackage toolset) to add raster mosaics Your GeoPackage is now ready for use. Note on sharing: You can upload a .gpkg file to ArcGIS Online, the file type will be recognized. You can send a link after sharing the item and others can then download it from the content gallery. Advanced topic: Because it is based on SQLite, GeoPackage comes with a database engine and good SQL language support. There are 3rd party tools for working with SQLite which you may find useful, but to include a spatial component in your work the ArcGIS Data Interoperability or Safe Software FME products support scripting SELECT, CREATE, DROP, DUPLICATE, TRUNCATE and CROSS JOIN statements within Spatial ETL tool transformers like SQLCreator and SQLExecutor. This approach enables very powerful and performant use of a GeoPackage.
... View more
08-14-2019
06:47 AM
|
5
|
4
|
8189
|
|
POST
|
Todd. how about this: create a shortcut for the Data Inspector app at C:\Program Files\ArcGIS\Data Interoperability for ArcGIS Pro\fmedatainspector.exe and open it whenever you want to, well, inspect any data. You can browse to the data or drag files into the app. Don't forget to set your background map in the FME Options area. We're thinking of adding a control in the Analysis ribbon alongside the Workbench control to start Data Inspector. Once you are done visualizing the data you can even Save As (say) File Geodatabase, just like doing a Quick Import. Anyone else looking at this thread, do you like the idea of surfacing Data Inspector to the ribbon?
... View more
08-12-2019
06:35 AM
|
1
|
1
|
1962
|
|
POST
|
OK then that's a good question. Historically we didn't have all of FME's functionality, like raster/imagery processing and writing, but a couple of releases ago we decided to include as much of FME as possible, so now (Pro 2.4, 10.7) you'll find very few formats or transformers different - basically things we cannot license. In one area - DBMS connectivity - Data Interoperability includes connectivity you'll find only in individual targeted FME editions. Another area we differ is Data Interoperability does not publish to FME Server from within Data Interoperability Workbench - if you would like that we can take a look at it. You can use a Data Interpoerability workspace with FME Server, just not from Workbench we ship.
... View more
08-09-2019
02:25 PM
|
0
|
0
|
1962
|
|
POST
|
David we have the same GeoJSON support as FME in Data Interoperability, meaning in the Workbench application. Have you found any issues?
... View more
08-09-2019
02:08 PM
|
0
|
2
|
8690
|
|
POST
|
Todd, it is our ETL solution, here are some links to get you started: Open Platform, Standards and Interoperability One more point: We are seeing less file-based formats in use (barring CAD, which we support in core), and in the case of GeoJSON, the source is often a URL, which the core JSON to Features tool can accept as an input provided the URL triggers a download.
... View more
08-09-2019
01:34 PM
|
0
|
7
|
8690
|
|
POST
|
Hi Joshua, this is one of those cases people might not thank us for introducing a weakly typed read-only layer. It would have to be like CAD, split by geometry class contained in each file and scanned for each file to figure out an attribute schema, which might change file to file. Personally, with Data Interoperability available, if i had to deal with consistent GeoJSON from some supplier on a regular basis I would create a custom format in Workbench (note to self, needs better doc) to output a designed and repeatable attribute schema every time and use Quick Import to bring the files in.
... View more
08-09-2019
01:27 PM
|
0
|
1
|
8690
|
|
POST
|
Hello Todd ArcGIS Data Interoperability for Pro does not support direct read of non-native formats like ArcMap does. The GeoJSON file has to be converted to a recognized format like Geodatabase. The core tool JSON to Features can do this, or you can use Data Interoperability Quick Import or a Spatial ETL tool or interactively by starting Workbench from the Analysis ribbon.
... View more
08-09-2019
12:05 PM
|
1
|
12
|
8690
|
|
POST
|
Hi Joshua, I never heard of EWKB/T, who needs that surprise, but like you show, easily handled. I'll request it be supported as a geometry encoding in Data Interoperablity.
... View more
08-02-2019
02:45 PM
|
0
|
1
|
7139
|
|
POST
|
Hi The data is not well formed, it contains hex-encoded WKB but is prepended with a 0 and newline character. I attach the source for a Data Interoperability ETL tool that reads the geometry after discarding the leading junk. You can use this with FME too.
... View more
08-02-2019
08:00 AM
|
1
|
0
|
7138
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 4 | 05-28-2026 05:58 AM | |
| 1 | 05-15-2026 06:54 AM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|