IDEA
|
Rob can you share a link to the issues for the field map view? Thanks.
... View more
07-10-2024
12:59 PM
|
0
|
0
|
310
|
IDEA
|
You could add a script tool to the Quick Access toolbar that has a table input and writes CSV to the project home folder.
... View more
07-03-2024
12:02 PM
|
0
|
0
|
207
|
POST
|
I think you can use the one Reprojector transformer, then after that use a FeatureTypeFilter transformer to split the data into separate streams. If Reprojector objects just use one per input feature type.
... View more
06-28-2024
09:34 AM
|
0
|
1
|
283
|
POST
|
Ah, well that's one for your system administrator! I guess your account will need some tweaking.
... View more
06-06-2024
10:12 AM
|
0
|
1
|
853
|
POST
|
Hello again Adam Luckily selecting a 3.9+ vanilla interpreter finds the ArcGIS one, quite frankly I forget the logic under the covers but anyway you're making progress. Safe's FME Flow software is definitely not installed by Data Interoperability. Automation of the fmw via Task Scheduler should work. To make it easier it can be useful to uncheck the publication of input parameters so they don't have to be supplied on the Python command being run. Automations typically connect to internet data sources anyway so it's the data that changes, not the source.
... View more
06-06-2024
09:02 AM
|
0
|
3
|
858
|
POST
|
If you're creating a workspace on an ArcGIS Enterprise server using fmeworkbench.exe to open Workbench and you are logged in as the arcgis service owner account it should work. You will need to set your FME Options translation Python interpreter to the ArcGIS option (3.9+?) and make sure your workspace also uses the same interpreter. Now for where I'm confused, when I have built a workspace on a server and want to automate it I run it and grab the Python command from the log an use Windows task Scheduler, which circumvents ArcGIS Server but does work. How to use FME Flow on the same machine I have no idea!
... View more
06-06-2024
06:28 AM
|
0
|
5
|
869
|
POST
|
Michael the single quotes around PARCELID make it a literal and not an identifier. Just remove them.
... View more
06-03-2024
02:05 PM
|
0
|
4
|
591
|
DOC
|
In an earlier post I enumerated common data source types that you will encounter when bringing data into ArcGIS. This document discusses one of these data patterns - common file types available on your computer or by simple manual download. The particular scenario discussed in the attached document is a CSV file with commonly found ETL requirements: Controlling the output geodatabase feature class schema and creating geometry from a column. ModelBuilder in ArcGIS Pro 3.3 is the automation environment - it has everything you need, and preserves work for on-demand re-use. The post attachment includes the discussion document and Model, but not the subject data, which you can download yourself. Please use this post to ask questions or comment.
... View more
05-24-2024
07:32 AM
|
0
|
0
|
127
|
DOC
|
In an earlier post I enumerated common data source types that you will encounter when bringing data into ArcGIS. This document discusses one of these data patterns - calling an API that requires pagination to retrieve a complete dataset. Pagination is a technique used by data publishers to manage load on their servers. Response payloads are typically JSON or CSV. Please read the attached document and use this space to ask questions. The post attachment also includes the ArcGIS Pro 3.3 toolbox discussed, but not the subject data.
... View more
05-24-2024
07:23 AM
|
0
|
0
|
156
|
BLOG
|
Kyle, I have asked a colleague in the geocoding team to respond, I'm not aware of any new functionality - thanks.
... View more
05-23-2024
08:24 AM
|
1
|
0
|
371
|
DOC
|
One-page "cheat sheet" documents are always popular, for example in the context of ArcGIS a perennial favorite has always been the functionality matrix for ArcGIS Enterprise. When considering your inbound ETL options there are high level decision criteria, this document (available as PDF in the post download) is a brief summary of two of them, namely where your source data comes from and how often you need to bring it in. This is only light guidance, in many cases you will have multiple implementation options, so treat this as an invitation to have a discussion, including in this community space. ETL Patterns
... View more
05-20-2024
08:14 AM
|
0
|
0
|
257
|
POST
|
My guess is Quick Import's input data type is not supported in the geoprocessing framework so you can try making an embedded Spatial ETL tool that accepts a file input. However a workspace (geodatabase) output is not supported by server side geoprocessing, so you will need to write to a zipped file geodatabase and make its path an output.
... View more
05-06-2024
07:56 AM
|
1
|
0
|
462
|
POST
|
Quick Import will always try to create a new file geodatabase and the scratch GDB already exists, try using another name and make sure it doesn't exist before running Quick Import.
... View more
05-06-2024
06:35 AM
|
1
|
2
|
475
|
POST
|
Tom, if you have remaining errors please open a support call. My guess is the geometry type suffix is an artifact of the reader not knowing the input geometry type, workspace generation will automatically create one (geometry named) feature type per input in those cases.
... View more
04-24-2024
06:24 AM
|
1
|
0
|
505
|
Title | Kudos | Posted |
---|---|---|
4 | Tuesday | |
1 | 2 weeks ago | |
2 | 3 weeks ago | |
2 | a month ago | |
1 | 08-20-2024 08:33 AM |
Online Status |
Offline
|
Date Last Visited |
44m ago
|