Latest Contributions by BKS

‎02-02-2021

Hi Shwu-jingJeng, I'm impressed at how fast you were able to decipher the issue and provide a solution. This worked like a charm. I was able to see the Cree in S123 Connect (Win10), S123 (Win10 app) and on my android device just fine. The geopoint question widget does not auto translate to Cree but that is what I expected. Have to admit I don't install fonts on my Win10 laptop often (ok never) but all I had to do was double click on the TTF file you provided and chose install. So I guess the issue really comes down to Windows only. That is, on MacOS and Android it works. I'll assume for now it will work on iOS as well for the S123 app. Thanks again ! Cheers, Brian ps - before you provided that truetype font, I tried loading Cree language on my Win10 laptop (see attached). After I did so I could see the Cree in the XLSForm and the Connect app and Win10 S123 app. But it size was too small. It was only after I loaded your font that it worked fine.

‎02-02-2021

Hello I've created a survey with support for three languages: English, French and Cree. I believe all is good with English and French setup. RE: the Cree language I was not hoping for it to work perfectly since Cree does not seem to be supported (can no longer find that link where I read that). My recollection was that for languages that are not supported, it was referring to 100% support meaning that in some cases (e.g. geo questions) the widget instructional text will not be translated. However, I cannot get any of the translated text to appear as a label. It takes up space on the form but it is not visible; either in S123 Connect or S123 Survey app. Yet, in the Excel form it appears just fine. ᐊᒥᐢᑿᒌᐚᐢᑲᐦᐃᑲᐣ Here are some Cree syllabics that I copied into a label field using the Cree (cr) language code; same as I did with French (fr) and it worked as expected. I'm not looking for perfection but if we can get most of the survey translated (less widgets, etc) that would be worthwhile. Thanks for any input. Brian

‎10-25-2020

Hello Zachary, Thanks for confirming the issue. And many thanks for the work-around. This seems to work. Regards, Brian Brian K. Schwarz Consulting Inc., Ottawa, Canada

‎10-20-2020

Using version 3.10 of ArcGIS Survey Connect, I've used body::esri:inputMask of (999)999-9999 to ensure the format for phone number input. On iOS and Windows field app all works fine. However, using Android field app, when entering the phone number, after typing the 3rd digit it disappears after entry. It's hard to explain but entering 10 digits will not enter a valid phone number format as it does on iOS and Windows. It's broken to the point where it is not usable. Hate to not use this formatting. Any other experience same? Any workaround? Thanks, brian

‎10-24-2018

Last year I used PyScripter 32bit to write scripts leveraging arcpy. I had installed the 64 bit BG since some of my geoprocessing tasks required the access to greater memory space than 32bit allowed. Once I installed 64 bit BG all worked just fine. I am looking to pick up these scripts and continue development but I can't seem to configure PyScripter 32 bit to run the 64 bit python interpreter. In the python interpreter window it only shows the 32 bit interpreter. When I run python from CMD window it brings up the AMD 64 bit version (in Win32). I can run my scripts from here bout would prefer to run them from within PyScripter. I've tried everything I can think of (apart from moving to PyCharm or ArcGIS Pro). Currently using Pyscripter 3.4.2 (32 bit), ArcPy (64 bit BG), ArcGIS 10.4.1, Windows 10 Shortened version of question to you: How exactly do you "After the 64-bit Python interpreter is installed, you can point PyScripter to use it instead of the 32-bit one." See attached CMD window and PyScripter Interpreter window.

‎05-08-2018

I'm working to clean up GIS attribute values that are outside assigned domains. There are approx 50+ domains on several fields and the enterprise GDB is reasonably large. I could write a SQL based solution but have been investigating Data Reviewer to see if it could identify all of the occurrences where attribute values did not match domains. I have figured this out and have written results to Reviewer Table but I would like to see in the Reviewer Table, the attribute value that falls outside the domain. As far as I can tell the Reviewer Table only provides the OID of the feature and in the Description the attribute name that does not match the domain; but no attribute value. Is this something I can have added using out-of-box Data Reviewer extension, or should I look for a custom solution??? Thanks for any info, Brian

‎05-14-2013

There is a bug that is fixed at 10.2- NIM076948- The arcpy.da.SearchCursor() where clause does not work with a table view. NOTE: As a work-around I successfully copied the table view to an in_memory table using CopyRows. This solved the problem since arcpy.da.searchcursor with where clause works if the source is a table as far as I understand the bug. Brian

‎05-13-2013

Thanks - I couldn't think of anything else to try. What's strange is that it does work sometimes. I don't know how to see the contents of the bug so can you tell me if the arcpy.searchcursor works on a table view with a where clause (i.e. is this limited to arcpy.da.searchcursor)?

‎05-13-2013

The field names will change when you use the 'AddJoin' tool, and this is most likely the issue. The new field name will be <feature class/table name>.<field name>. Wish that was the problem but already handle that. I print the expression and try the same expression on the table manually and it works just fine. Technically I use CopyRows to copy the table view (that includes the join) to a table in the fGDB. Then I copy the expression used from the code and it works. The one think I needed to do was change the "." character to a "_" character since this is what happens when you save a table with a join to a fGDB. I assume the fGDB doesn't like "." in field names so it converts to "_".

‎05-13-2013

Just wondering if anyone has had any trouble with using a query expression with arcpy.da.searchcursor? I've used this successfully many time but I have code where I create table views from tables in a fGDB then use a cursor on selected records using arcpy.da.searchcursor. One of these works fine while the other does not reduce the number of records from the total records in the table. I've stared at this for a while and really don't see a reason why one would work and the other does not. The only think I can think of is that the table view that does NOT work has a joined table associated with it using AddJoin. Otherwise there is no significant difference that I can see between the two. One other thing I did try was to using CopyRows to copy the table view to a table, use MakeTableView using the same query expression used above in the arcpy.da.searchcursor, and then use CopyRows to a copy the view to table. After this runs, the final table copied behaves as if the query was not applied (same as happens in arcpy.da.searchcursor). any leads appreciated.

‎04-29-2013

Caleb and Chris, Thanks for info. This was helpful. Forgot to update this earlier. Cheers, b

‎04-22-2013

Perhaps I can calculate the Shape_Area setting equal to Shape.Area. But would still like to know if this is a bug or can someone set me straight (or provide best practices) on when to assume "Shape_Area" and "Shape_Length" fields are created/updated with respect to overlay tools? Thanks, b

‎04-22-2013

Question re: Shape_Area on Intersect output While in ArcMap, if I direct the output of the Intersect tool to "in_memory", why is it that the "Shape_Area" and "Shape_Length" fields on the output layer table are both set to Null for all rows? If I do same on disk these fields are auto calculated. Reason I ask is that I was automating this in python and made the assumption that "Shape_Area" would be updated based on Intersected polygon properties. Is this a bug or can someone set me straight (or provide best practices) on when to assume "Shape_Area" and "Shape_Length" fields are created/updated with respect to overlay tools? Is there a simple and fast way to update these fields while in_memory? Thanks so much, b

‎03-06-2013

Thanks - that's so obvious I didn't see it. Appreciate your patience. b

‎03-06-2013

Hello Caleb1987, Thanks for all of that info. I did know some of that but it's good to get more info and is appreciated. Although I DO import arcpy into both aaa.py and bbb.py, you've made me realize why I'm getting the error I think. That is, when I run bbb.py which imports both arcpy and aaa.py, and attempt to execute aaa.func1(), the reason there is a problem with aaa.func1() not recognizing 'arcpy' is that it never gets imported into aaa.func1() since it's only imported in aaa.py when name == __main__ (i.e. when executing aaa.py directly). So I do get this. But what is the solution then? Should I add "import arcpy" to each function within aaa.py ? This does solve the problem but it doesn't seem like the right thing to do. Not sure if this will create any issues (performance or otherwise). Any thoughts? Cheers, b

Online Status	Offline
Date Last Visited	‎08-07-2024 09:13 PM

My Ideas

Latest Contributions by BKS

Re: Support for Indigenous language Cree

Support for Indigenous language Cree

Re: body::esri:inputMask with (999)999-9999 on Android

body::esri:inputMask with (999)999-9999 on Android

Re: Memory issues with a large dictionary

Data Reviewer 10.5 Domain Check

Re: arcpy.da.searchcursor with expression

Re: arcpy.da.searchcursor with expression

Re: arcpy.da.searchcursor with expression

arcpy.da.searchcursor with expression

Re: Shape_Area ?

Re: Shape_Area ?

Shape_Area ?

Re: problem using python modules

Re: problem using python modules

Re: Edit Creator field of hosted feature service

Re: s123 Connect UI

Re: Alternative to Esri's Survey123 Reporting Syst...

Printing EB scrolling page to PDF

Reducing survey size vertically