|
POST
|
That's not quite correct and I'm sure this is a source of much confusion. You can still create DBs in SQL express (desktop or workgroup edition DB server) wirh ArcMap and then work with them just fine in Pro. You cannot CREATE those DBs in Pro, however. I don't understand how Pro will be a full replacement for desktop with major functionality like this still missing. I don't understand how after years of users asking the same/similar question that Esri cannot clarify the roadmap here. Should we start planning that 2way replica environments will no longer be possible without a full ArcGIS Server Standard license for both participating DB instances??
... View more
10-09-2020
05:11 AM
|
3
|
5
|
8515
|
|
POST
|
All I'm seeing from multiple threads is that there is absolutely no way to create a GDB in SQL Express with Pro.
... View more
10-08-2020
06:30 AM
|
2
|
1
|
8515
|
|
POST
|
I honestly feel like Esri is just ignoring this. How is it I need to have ArcMap just to create a GDB in SQL Express?
... View more
10-08-2020
06:29 AM
|
3
|
0
|
1788
|
|
POST
|
Ok, I see. What if you put your SDE connection files in a shared network location and have your script point to those? The location would have to be made available to the ArcGIS service account. Not sure if you used a domain or local machine account for your server setup.
... View more
06-18-2020
05:50 AM
|
0
|
1
|
2292
|
|
POST
|
Have these various DB connections been registered with your Server's Data Store?
... View more
06-17-2020
11:28 AM
|
0
|
3
|
2292
|
|
POST
|
Is there a list of ArcPy functions that can use feature services directly for input? For example, arcpy.da.TableToNumPyArray will happily use a FS REST endpoint URL directly as an input and from there you can do all the awesome NumPy stuff you want. On the other hand, arcpy.MakeFeatureLayer_management will not accept the URL as an input. It will accept the layer reference in the TOC if the feature layer is added to Pro and you are using the Python window. The issue isn't solved with the ArcGIS Python API. Yes, there is the arcgis.features module, but despite being able to call up a Portal item as a 'Feature Layer', this cannot then be passed to an ArcPy function. The Python API is great for a lot of things, but obviously doesn't leverage all the power that ArcPy brings to geoprocessing. So, is there a list of arcpy functions compatible with feature services? Perhaps the Data Access module is the only set of functions that is?
... View more
06-17-2020
10:29 AM
|
0
|
0
|
682
|
|
POST
|
I tried what Dale Jackan suggested. I did this from a fresh clone from a clean 2.5 install. I can't even up update python via Conda! Dan Patterson
... View more
06-03-2020
10:45 AM
|
0
|
4
|
2726
|
|
POST
|
I too give up. I CANNOT get spyder of any version to install with 2.5. I've done more clean-clean uninstalls of the entire environment than I care to remember, I've done via Python command line, i've tried over and over again with the stupid package manager. I just want my Spyder IDE. The most recent failure of trying to install from the command line corrupted my cloned environment and all the jupyter labs & extensions all ruined. I've tried tech support and the analyst is convinced it is because of my (work at home) internet speed! None of this should be so hard! Hours upon hours wasted again!
... View more
06-02-2020
03:04 PM
|
1
|
0
|
1946
|
|
POST
|
This ArcGIS Blog post by Hussein Nasser is what inspired my interest in finding a way to do this. Basically I'd like to create an attribute rule where a user collects/creates a point (probably Collector) and this then updates a polygon which the point falls within/intersects. Imagine the polygon feature class being something like zip codes, or census units and the attribute field getting updated is something like simply indicating that the person has visited that location or even more simply that the polygon feature/record itself as been visited. I suppose there might be a way to achieve this with a relationship class as well. Thanks for any ideas anyone may have!
... View more
05-12-2020
06:30 AM
|
0
|
1
|
791
|
|
POST
|
Thanks Lukas, Now i need to wrap my head around the suggested workaround as I'm not quite clear on that yet...my brain is fried from spending days trying to research this problem.
... View more
04-21-2020
10:16 AM
|
0
|
1
|
2241
|
|
POST
|
Completely stumped here. I have seen a handful of somewhat similar threads dealing with Lambert Azimuthal Equal Area...the problem here is working out the proper transformation. Here's a bit of a summary of what I do know. This (NDVI) data can be obtained from USGS here [AVHRR in this example]. I have other data I am trying to align with this data (GCS_North_American_1983 WKID: 4269). There is no WKID associated with the data's projection info, nor is there a GCS or datum. When searching for 'LAEA_Sphere_19', surprisingly, only a handful of results are returned. One result provides some additional insight. Spatial Reference .org lists this as "SR-ORG Projection 8750 - eModis Phenology" The ESRI WKT reflects exactly what we see in the raster's spatial reference properties: PROJCS["LAEA_Sphere_19",GEOGCS["GCS_unknown",DATUM["D_unknown",SPHEROID["Sphere",6370997,0]],PRIMEM["Greenwich",0],UNIT["Degree",0.017453292519943295]],PROJECTION["Lambert_Azimuthal_Equal_Area"],PARAMETER["latitude_of_origin",45],PARAMETER["central_meridian",-100],PARAMETER["false_easting",0],PARAMETER["false_northing",0],UNIT["Meter",1]] The raster metadata provides no additional insight. There is much discussion (and stories of headache) in dealing with the Sinusoidal projection associated with other USGS/NASA MODIS data, but this is not that projection. Out of desperation, I tried creating the custom geographic transformation found here...of course that failed to yield proper results. This was another dead-end waste of time. The various online tools associated with manipulating the USGS/NASA HDF files are not valid for this data. This are TIFs for NDVI Phenology. My source data is GCS_North_American_1983; i need to somehow match to this LAEA Sphere 19. Please, any insight or help here would be most appreciated...I cannot believe how little documentation there is regarding this!
... View more
04-21-2020
07:38 AM
|
0
|
3
|
2348
|
|
POST
|
From Support Services: We finished the testing and confirmed and attached the following defect to your case: BUG-000129805 : Running the python command for Layer to KML works in idle, but fails to create output if run from script tool. Lame. We are in the process of updating all of our existing GP services to Pro/Python 3.x based tools. This roadblocks updating one of our most used GP widgets which will now have to remain ArcMap/Python 2.x based for the foreseeable future.
... View more
04-02-2020
06:26 AM
|
0
|
0
|
3720
|
|
POST
|
Dan, I tossed this into a script tool with the script imported. The TBX is zipped and attached above. The output location will be a folder called 'export' in your scratch folder. Thanks!
... View more
03-30-2020
08:03 AM
|
0
|
0
|
3720
|
|
POST
|
Hi Dan, I dumbed th code way down for purpose of isolation. No parameters set in the script tool for this test. I have tried a number of different input types and output locations. Humor me and toss that in a script tool and let me know if it works for you. This may be a bug.
... View more
03-28-2020
06:26 AM
|
0
|
2
|
3720
|
|
POST
|
ArcGIS Pro 2.5 The Layer to KML GP Tool from the standard TBX works fine. The ArcPy code will work in the Python window. The ArcPy code will even run and produce the KMZ from an IDE (such as Spyder). The ArcPY code completes without error when run as a Script Tool in Pro, but no output is produced. Can anyone else test this? I'm losing my mind trying to figure this out. import arcpy
arcpy.env.overwriteOutput = True
arcpy.MakeFeatureLayer_management(r"C:\Users\JackTorrance\Documents\ArcGIS\scratch\export\ExportTestAgain333.shp", "ExportedFeaturesLayer")
arcpy.AddMessage(arcpy.GetCount_management("ExportedFeaturesLayer").getOutput(0))
arcpy.LayerToKML_conversion("ExportedFeaturesLayer", "D:\\TEMP\\TryThis.kmz") I added the message simply to ensure the feature layer was valid (contains features), and you can see this working as expected in the GP messaging dialog. One other observation: the script tool takes way longer than it should, like 2.5 minutes!
... View more
03-27-2020
06:22 AM
|
0
|
7
|
3861
|
| Title | Kudos | Posted |
|---|---|---|
| 9 | 03-24-2026 11:41 AM | |
| 1 | 11-06-2024 06:58 AM | |
| 1 | 12-16-2022 07:01 AM | |
| 1 | 08-09-2024 06:55 AM | |
| 1 | 08-13-2024 05:58 PM |
| Online Status |
Offline
|
| Date Last Visited |
03-24-2026
12:51 PM
|