|
POST
|
Sara, Could you provide a short example of what you're seeing? The output number you're showing does look like the VT_DATE object that is used internally in some formats for representing a date, but it shouldn't be displayed that way within ArcGIS. Thanks, Shaun
... View more
12-01-2017
09:39 PM
|
0
|
2
|
1549
|
|
POST
|
Hello Karen, Yes, those instructions should work for the offline installation. If you have ArcGIS Pro, you can also install the package from within the application -- visit Options > Geoprocessing, and at the bottom of the panel you can select the version of R. It should by default write the package to your Documents folder. Cheers, Shaun
... View more
11-08-2017
09:30 PM
|
0
|
1
|
1471
|
|
POST
|
Ah yes, thanks. Yes, this is a problem with the Windows C Runtime (UCRT) that is shipped with ArcGIS Pro 1.4 and earlier. We've fixed the problem in ArcGIS Pro 2.0, if you can upgrade. Cheers, Shaun
... View more
10-24-2017
10:10 PM
|
1
|
0
|
4837
|
|
POST
|
Sebastián, no problem, happy to help. Yes, you're right -- it's supported in the same versions of Server as Desktop. So Server 10.3.1 or newer will work. Cheers, Shaun
... View more
10-24-2017
10:46 AM
|
1
|
1
|
2780
|
|
POST
|
Hello Yasunari, Could you share what version of ArcGIS Pro you're using, and what version of Windows? Could you also run this from the Python prompt in Pro: import locale, time
local.setlocale(local.LC_ALL, 'ja')
time.strftime('%a') Does that produce the same error? Thanks, Shaun
... View more
10-24-2017
06:27 AM
|
1
|
2
|
4837
|
|
POST
|
Following up on what Marjean wrote, we've released a new version of the bridge which should address this regression for Pro users. As Marjean says, it's even easier in Pro to use the built-in installer, but if you'd like to use the toolbox, try downloading it again and the toolbox should now open. Cheers, Shaun
... View more
10-20-2017
12:50 PM
|
1
|
0
|
5498
|
|
POST
|
Sebastián, You're right that we haven't documented this, I'll add an issue to my list for adding instructions on this. Here's the basic process: Install R on the Server. You'll want to make sure to install the 64-bit version of R. Install any packages you intend on using in R (you can also do this in your geoprocessing script, but it's best practice to do it beforehand). Install the R-ArcGIS Bridge on Server. You can do this through R directly, see this screencast. Create your Geoprocessing Service that references R as you would create a Python service. With the necessary pieces in place, it should execute like any other GP Service. Let us know if you have any further questions, Cheers, Shaun
... View more
10-11-2017
09:11 PM
|
1
|
3
|
2780
|
|
POST
|
Naresh, To overwrite an existing data source, just pass the location that you'd like to write to during your `arc.write()` call. Provided that the data source isn't locked, it should overwrite the existing data at that location. Cheers, Shaun
... View more
10-11-2017
09:05 PM
|
1
|
0
|
1294
|
|
POST
|
Brian, Thanks for the question, this is something that I'll add a note for me to document in the package documentation. To reference a database, there are a couple of approaches: If you only need access to one layer: you'll need to create a layer file which references the data. You should be able to do this from within ArcMap or Pro by right clicking on the layer > Save as Layer File, if it's in your current map, or right click the layer in the Catalog pane and select "Create Layer". Once you've created that layer file, you can reference it directly with arc.open(), and it'll work like any other data source. If you want to access arbitrary layers in your database: instead of creating an intermediary layer file, you can directly reference things from the .sde file. This file is created when you add a database connection, by default it'll end up in your user profile. You can find it from ArcMap for example by right clicking on the database, selecting Properties, the 'Name' field contains the full path to the sde file. You can copy this elsewhere, or reference it directly, using the syntax: r <- arc.open('c:/path/to/my.sde/dbname.layername') The bridge doesn't currently have the underpinnings to figure out the necessary information directly, but either of the above approaches will give you direct access. Let us know if you need anything else. Cheers, Shaun
... View more
10-11-2017
08:03 PM
|
1
|
0
|
1977
|
|
POST
|
Are you getting that error after import arcpy, or from a Python.exe session without any further steps? I'd try renaming your existing arcgispro-py3 directory, then running the repair for ArcGIS Pro 2.0, and it should lay down a new initial valid copy of the arcgispro-py3 environment. Cheers, Shaun
... View more
09-15-2017
02:10 PM
|
1
|
0
|
2581
|
|
POST
|
James filed an issue on Github, and we were able to track it down to an invalid Python install. After reinstalling ArcGIS, he's up and running again. Cheers, Shaun
... View more
09-14-2017
09:47 PM
|
0
|
0
|
2233
|
|
POST
|
Hi Matt, I don't think there's any single location for tips like this. I agree it'd be nice to have, an "ArcPy patterns" resource which collected together these kinds of approaches for making Python development simpler. I'll ask around. Cheers, Shaun
... View more
09-14-2017
09:09 PM
|
1
|
0
|
5030
|
|
POST
|
Dave, I can reproduce this issue locally. Despite the 64-bit DLLs involved, the memory limit is being capped at what you'd expect for a 32-bit process (2GB). I'm looking into this issue, it looks like its a default value that is being set by R, but it isn't clear to me why that is yet. In the meanwhile as a workaround, you can add this to the top of any scripts you're working with that need more memory: limit.mb <- as.numeric(
gsub("TotalVisibleMemorySize=", "", gsub("\r", "",
system('wmic OS get TotalVisibleMemorySize /Value',
intern=TRUE)[3]))) / 1024
set.limit <- memory.limit(limit.mb) That will set the memory available to R to the total memory available on the machine. Cheers, Shaun
... View more
09-14-2017
11:42 AM
|
1
|
1
|
1105
|
|
POST
|
Andrew, I can confirm the issue when working with Logical values. None of the ArcGIS Field Types directly map onto a boolean, so by default its mapping these to values it knows how to encode. I've created a new issue for this here: Support mapping logical values into the closest supported type · Issue #13 · R-ArcGIS/r-bridge · GitHub I also can confirm that writing long text values into a new output file doesn't work. I've filed a second issue for that here: Support writing text fields which are longer than 255 characters. · Issue #14 · R-ArcGIS/r-bridge · GitHub Both of these are things we intend to fix, I'll update this thread and let you know when we've made a release which fixes these issues. Cheers, Shaun
... View more
08-02-2017
02:55 PM
|
0
|
1
|
2339
|
|
POST
|
OK, I did a little more digging. Basically, some software like OGR will write NULL values into a DBF. It does this by writing out 0x2a in the place where a value would normally exist, which indicates the particular record is "deleted". OGR, and software based on OGR do support this, but this is a deviation from the Shapefile whitepaper, and as such ArcGIS doesn't directly support this, independently of using the bridge. NULL values work fine to Geodatabase outputs.
... View more
08-02-2017
02:03 PM
|
0
|
0
|
2339
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-24-2025 09:10 PM | |
| 1 | 08-12-2022 10:14 PM | |
| 1 | 05-05-2025 10:56 AM | |
| 1 | 04-04-2025 09:03 PM | |
| 1 | 02-09-2023 10:10 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|