|
POST
|
I just checked, and it does appear to be fixed. My hyperlinks in Open Data are now pointing to the correct license.
... View more
09-28-2017
09:21 AM
|
0
|
0
|
1212
|
|
POST
|
Super helpful! Thanks. For those that would like a Python option.... here's a gist of something I cobbled together: Give this script a geodatabase (Personal, File, or SDE connection) and it will remove the "Geoprocssing History" content…
... View more
08-30-2017
03:57 PM
|
2
|
0
|
1372
|
|
POST
|
I got the size from a query Esri support suggested. It went from 60 MB to 25 MB. That means there was 35 MB of GP history in the metadata that got deleted. I don't know why it takes so long to read 35 MB of data for modern software, but that's the way it goes with Esri software. It can do amazing visual gymnastics with 3D data in realtime, but it takes over a minute for it to read 35 MB of text, essentially. Go figure.
... View more
08-15-2017
02:10 PM
|
1
|
2
|
5436
|
|
POST
|
Updated: Discovered the issue: Metadata Geoprocessing History Cleared out the Geoprocessing History from the Metadata for our large SDE geodatabase by running this Python code in ArcMap's Python Console. ##Change this to point to your SDE connection file gdb = r"C:\Users\...\AppData\Roaming\ESRI\Desktop10.5\ArcCatalog\SDE@YOURGDB.sde" ##Change this to match your file structure and location remove_gp = r"C:\Program Files (x86)\ArcGIS\Desktop10.5\Metadata\Stylesheets\gpTools\remove geoprocessing history.xslt" ##Change this loaction to a temp folder to output the XML name_xml = r"C:\temp\cleanup_staging" arcpy.XSLTransform_conversion(gdb, remove_gp, name_xml, "") arcpy.MetadataImporter_conversion(name_xml, gdb) print 'completed' This reduced the size of our GDB by more than 50%! After that, when in ArcGIS Pro, connecting to the GDB went down from 1.25 minutes to just 5 seconds. Fantastic. The bonus is that it sped up connection times to SDE in ArcMap as well. Thanks Esri support!
... View more
08-10-2017
11:18 AM
|
5
|
6
|
5436
|
|
POST
|
Thanks for the recommendation. There have been no upgrades on this machine. It's all fresh installs on a new Win 10 Pro OS. The part to remember is that ArcCatalog works just fine. ArcGIS Pro is slow. This was also the case with my older Windows 8 OS, with ArcGIS Pro 1.4 and ArcGIS Pro 2.0. All things begin equal, ArcGIS Pro is very slow with this large SDE connection and doesn't remember connections. ArcCatalog works like a champ. The network is fast, the database server is fast, everything is fast. ArcGIS Pro is slow with the large SDE connections. This was true on my previous setups and is still true today with a new setup. Plus that Esri expert admitted they had issues with Pro doing buggy stuff with SDE connections. I'll create a support ticket.
... View more
08-04-2017
09:18 AM
|
1
|
0
|
5436
|
|
POST
|
We have ArcGIS Pro 2.0, and we are trying to connect to our main SDE geodatabase, but it's painfully slow, to the point of making it practically unusable. Our SDE geodatabase has 380 feature classes. It's a beast, but ArcCatalog takes just 20 seconds to connect up once, and then it's fast for the rest of the session. However, in Pro, if we even touch (not double click, just a single click) our large SDE geodatabase connection icon to view the "Details" of the SDE geodatabase, Pro does the progress triple-bar thing for about a minute, evetually loads the Description metadata, but then proceeds to lock up Pro for another minute. This happens every single time we go away from the "Databases" folder and then return to it. Pro doesn't remember that it connected to the geodatabase just 5 seconds ago. So when we come back to the "Databases" folder the whole process starts over. What is going on in the background? At the UC 2017, I spoke with an Esri employee who stated that ArcGIS Pro 1.4 (and previous) had a bug where Pro would make "hundreds" of calls to each feature class for no functional reason. He then said that this bug was fixed in Pro 2.0, but it appears to still be an issue. He also advised indexing, which I've done (left the computer locked with me signed in, Pro running over night), but it also appears to have no positive effect. Anyways, our smaller SDE geodatabases work much faster, but you can still tell that Pro has to "reconnect" and gather some data from the gdb in the background. It just seems like Pro has taken a huge step backwards, contrary to advertisements of "64 bit speed", from ArcMap/ArcCatalog when it comes to interacting with SDE geodatabases. Can anyone explain why Pro is slower than ArcCatalog when interacting with SDE geodatabases?
... View more
08-03-2017
11:18 AM
|
7
|
12
|
9840
|
|
POST
|
I can see data in ArcCatalog preview. I can even see it in an ArcGIS Pro 1.4 map. But I do not see the same data inside he ArcGIS Pro 1.4 preview of a Project Database feature class:
... View more
01-27-2017
02:22 PM
|
0
|
5
|
2983
|
|
POST
|
Generally speaking, you don't need it. According to the documentation: Some transformations that require files are not installed with the ArcGIS Pro installation. You can download and install the ArcGIS Pro Coordinate System Data files at my.esri.com. The additional files are the EGM2008 and GEOID12b geoid models; VERTCON files; GEOCON v1; and three NTv2 files for Switzerland, XRail, and OSTN15.
... View more
01-26-2017
09:28 AM
|
2
|
2
|
5857
|
|
POST
|
I've noticed that all number field datatypes (except for ObjectID) are converted to string datatypes in the Shapefile downloads from Open Data Portal. For example, in the Open Data Portal for Washinton DC Parks, you can see there is a field named "Benches" with a Number datatype: However, once you download the Shapefile, the datatype is converted to String: This creates a hassle for people consuming this data if they want to symbolize based on numeric fields, because they have to convert the data in their GIS before they can symbolize using numeric data. Is this by design (if so, why?) or a oversite/bug?
... View more
09-15-2016
01:58 PM
|
0
|
1
|
1787
|
|
POST
|
The RSS feed link for Comment subscription in Open Data has minor typo, which is it has 2 too many slashes after 'http:' and 1 too many slashes after '.com': I tried in several browsers, seems to be something happening on the back end, probably based on some variable concatenation (my guess). Sorry if this seems nit picky 🙂
... View more
02-26-2016
12:07 PM
|
0
|
0
|
2199
|
|
POST
|
I'm sure you've probably figured out a solution since its been almost 1.5 years since you asked this, but I'll post the answer here for anyone who is having the same problem. With your situation, I'd recommend using this first method. However, if you ever need to manually change the Field Aliases in the metadata, then use the second method down below. First Method: Synchronize with SELECTIVE option Open up the Synchronize tool Give the tool your feature class, choose the SELECTIVE option. This updates everything except for the Title of your Metadata. Second Method: Manually Editing Open up the metadata editor in ArcCatalog. Second, go to the Fields section, Expand the drop downs to the field alias you want to update, update it, and then save your changes. Once you've done that, the Field Alias in the metadata will stay the same even if you change the Alias in the Feature Class itself.
... View more
02-04-2016
01:11 PM
|
0
|
0
|
1040
|
|
POST
|
Short Version: We are using a CC BY 4.0 license, but Open Data is changing it to a CC BY 3.0 license. Details For example (as of 1/20/2016, at 10:45 am), our ArcGIS Online feature layer "Parcel Situs Address" is using a 4.0 license: That content comes from the HTML embed code that comes directly from the Creative Commons site: However, when that same feature layer is viewed in open data, the hyperlink applied to the CC-BY image is changed to the "3.0" license: Can anyone shed light on what's going on here? The 4.0 license very similar to the 3.0 license, but it's definitely not the same. ArcGIS Open Data ArcGIS Open Data community
... View more
01-20-2016
10:44 AM
|
0
|
3
|
4471
|
|
POST
|
Are you adding the new layer to the bottom or the top of the existing map layers?
... View more
01-19-2016
04:33 PM
|
0
|
0
|
1381
|
|
POST
|
We are experiencing the same issue today. These warnings weren't here a few weeks ago when we last checked it. The only reason we noticed this is because our layers weren't showing up in search results on the global search page. I'm wondering if something widespread is going on. ArcGIS Online isn't reporting any issues, so maybe it's strictly an Open Data issue?
... View more
01-19-2016
04:27 PM
|
1
|
1
|
3594
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-20-2026 02:45 PM | |
| 3 | 09-15-2025 01:02 PM | |
| 3 | 12-06-2024 08:27 AM | |
| 1 | 03-07-2024 09:45 AM | |
| 3 | 12-04-2024 11:38 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|