|
POST
|
If you open a support call with the central issue asking what permissions are needed for SDE stored procedures in SQL Server you will get the response you need. FME is a red herring as its only passing the statements through but it will deter Esri owning the issue. Server team at Safe are a good resource too.
... View more
06-02-2022
07:09 AM
|
0
|
1
|
1814
|
|
BLOG
|
I would have to check with the Enterprise team but it does ring a bell that bi-directional collaboration is a recent feature. You can effectively 'sync' any combination of EGDB, Portal and AGOL datasets in both directions but you would have to figure out the business logic as to which system owns the desired feature state. For example field work might need to be ingested to the EGDB from Portal or AGOL feature services but separately some features added to the EGDB might need to be pushed to the feature services. This logic might be driven by created_date and edited_date, or key field comparisons for new features.
... View more
05-24-2022
11:06 AM
|
0
|
0
|
8241
|
|
BLOG
|
@AJ_devaccount Yes you can do this, scheduling from a Pro client is simplest but it can be executed on an Enterprise machine that has Data Interoperability installed if you need high availability. However, are you sure the core distributed collaboration does not meet your needs? Let's work through that before committing to the ETL approach.
... View more
05-24-2022
10:27 AM
|
1
|
0
|
8257
|
|
POST
|
I missed that you are working in ArcMap; the Create Fishnet tool is in the Data Management > Sampling toolset in the tool catalog tree:
... View more
05-23-2022
01:42 PM
|
0
|
0
|
2183
|
|
POST
|
It is here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/create-fishnet.htm You can also create an oriented fishnet: https://pm.maps.arcgis.com/home/item.html?id=9398bd2232cb4c8490b0b05015364d28
... View more
05-23-2022
01:11 PM
|
0
|
2
|
2210
|
|
IDEA
|
We do support table naming in mixed case unless the tables were created with delimited names, like "Type", people sometimes do this to protect reserved words for example. Is this your situation? Delimited names are not supported, however Data Inteoperability extension can read tables with delimited names.
... View more
05-13-2022
06:51 AM
|
0
|
0
|
1593
|
|
BLOG
|
@ClaudiaGIS Hi, yes sure, please email me as bharold at esri dot com - thanks.
... View more
04-27-2022
02:32 PM
|
0
|
0
|
3292
|
|
IDEA
|
@Anonymous User Can you comment? For Data Interoperability users, regarding Phil's question - yes we can 'see' Enterprise and Online feature services. Regarding the wider topic of no-code integration options like Power Automate, Make etc. I'm working on a sample using Data Interoperability where continuous integration is implemented and verified with a combination of scheduled feature service refreshes and triggered web tool actions in Enterprise, with the result validated from the webhook change set.
... View more
04-27-2022
09:06 AM
|
0
|
0
|
3714
|
|
POST
|
That looks like the file didn't download properly, we should have a better error message that does a checksum. Try downloading again, if it still fails open a support call.
... View more
04-08-2022
06:40 AM
|
1
|
0
|
2256
|
|
IDEA
|
I find that SQL statements for the use case can blow up on you when row counts are in the hundreds of thousands, for example leveraging the output of Generate Near Table.
... View more
04-04-2022
08:53 AM
|
0
|
0
|
748
|
|
POST
|
Hi Brittany, your feature service will have datetime fields stored in UTC so when upserting using Data Interoperability use the available datetime transformation functions to offset to UTC before writing.
... View more
03-31-2022
10:51 AM
|
1
|
0
|
2370
|
|
BLOG
|
Public safety geocoders in particular like to give cross-street names to first responders navigating to street addresses, their local knowledge helps them decide what streets 'book end' the block they are heading for. Building a locator that does this starts with getting cross street data into your street centerline feature class you are using for locator reference data. Here are some streets in Redding, California where I have derived cross street fields for a feature class, the pop-up relates to the selected street segment and I have highlighted the added cross street fields: Inspecting Cross Streets Made By The Tool ArcGIS Data Interoperability comes to the rescue here, especially the TopologyBuilder transformer. In the past I have done all sorts of math in Python to calculate data structures I can query for cross streets but I much prefer the no-code approach. If you go way back in ArcGIS, like some people I know, you may recall that arc-node topology was baked into the storage model for polygonal features. This is no longer the case in a geodatabase, nor is it easy to make - except with ArcGIS Data Interoperability. So that is what I used in the ETL tool in the post download (requires ArcGIS Pro 3.3 and the ArcGIS Data Interoperability extension): ETL tool that makes cross streets I'll let you surf the tool yourselves, but in thumbnail I read in street reference data, send the geometry, ObjectID and a full street name attribute into some processing that figures out cross streets, then join these back onto the street features and write out a new feature class. I don't include the data but it is publicly available so you can test drive the tool for yourself after repairing paths. In the download toolbox there is also a model that creates a locator (also included) with custom output fields for cross streets, and here it is in action with a 'What's Here?' query in a map. You can get to the area by a geocode to 2500 CELESTIAL ST, Redding, 96002 with the supplied locator. Cross Streets Returned By The Locator In production, street centerlines would often be used as one primary table in a locator that also uses point address data and zone features, and to access the cross street values from a geocode service you might have to use a category filter of 'Street Address'. If you need help putting this together please contact your local Esri representative or use the comments feature in this post, I'll be listening!
... View more
03-23-2022
11:32 AM
|
3
|
6
|
6440
|
|
IDEA
|
Hi, FlatGeobuf is in the GDAL drivers we ship in Pro. from osgeo import gdal, ogr
vformats, rformats = [], []
for i in range(ogr.GetDriverCount()):
name = ogr.GetDriver(i).GetName()
if not name in vformats:
vformats.append(name)
vformats = sorted(vformats)
for i in range(gdal.GetDriverCount()):
name = gdal.GetDriver(i).LongName
if not name in rformats:
rformats.append(name)
rformats = sorted(rformats)
print('Vector Formats:\n')
for format in vformats:
print(format)
print('\n')
print('Raster Formats:\n')
for format in rformats:
print(format)
print('\n') Not super easy but not too hard either to write a converter, let us know if you need help. Data Interoperability extension will support FlatGeoBuf at Pro 3.2.
... View more
03-21-2022
06:40 AM
|
0
|
0
|
5236
|
|
IDEA
|
Like this: https://pm.maps.arcgis.com/home/item.html?id=e638afe0695a4ad38388cb8d9b350446 Selections are propagated based on shared values of two fields, one in each layer/view.
... View more
03-17-2022
09:40 AM
|
0
|
0
|
4818
|
|
IDEA
|
This is the old Keyfile select capability from Arcplot, it is very much needed in Pro. I have emulated it with a script tool but its not ideal.
... View more
03-17-2022
09:27 AM
|
0
|
0
|
4825
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 5 hours ago | |
| 1 | 5 hours ago | |
| 1 | yesterday | |
| 4 | 05-28-2026 05:58 AM | |
| 1 | 05-15-2026 06:54 AM |
| Online Status |
Online
|
| Date Last Visited |
2 hours ago
|