Latest Contributions by KellyKoenig

Does the feature class you're making an attribute rule for have any unsaved edits? Maybe someone else is editing the feature class, or you have it open with unsaved edits in another project file. ... View more

Hmm. Maybe create a new FGDB with two new feature layers and import the field map schema from the original feature layers. Copy a handful of records from each original feature layer and paste them into the new feature layers (or create dummy polygon features that you fill in with a random "GRTS_ID'), then create the rule again. That would be a truer "clean slate" approach than exporting copies of the feature layers themselves. ... View more

I don't know of a way to adjust these items within ArcGIS Pro specifically, but you can change the display scale on your computer to increase the cursor/text size in all programs. I just tried it and it works in Pro. If you're running Windows 10, go to Settings -> Display -> and change the "scale and layout" option. See here for more info: How to Use Windows 10 Display Scaling  Hope this helps! ... View more

Owen Evans‌ Do you have any update on this timeline? Any ballpark date that we ca expect the announcement would be great, if you have that info. Thank you, Kelly ... View more

Try removing " tblLanding_EXPORT. " in line 2 so it says  var cityname = $feature.City; // read out the city var sql = "City" + " = '" + cityname + "'"; // create query var table = FeatureSetByName($map, "LandingsWithCables_EXPORT"); // get access to table var related_records = Filter(table, sql); // filter the table for relevant records var cnt = Count( related_records); // determine the number of records found var result = ""; if (cnt == 0) { // no records found result = "No cable systems found"; } else { // we have related records, let's create the text to return result = cnt + " cable system(s) found:"; for (var record in related_records) { var txt = TextFormatting.NewLine + " - " + record.SystemName; // use the correct field name from the table result += txt; } } return result;‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

The Export and Import XML Workspace tools sound like they would do exactly what you need, if you use the "Schema only" export & import options.  (Although I admit that I've used the method you described and never had any issues despite it not being "best practice," per see. Yet, at least! I may have just jinxed myself   ) ... View more

Great idea, Robert LeClair. In a similar vein, TKM ., you might have some luck solving the problem by checking the geometry for errors (more info on how to check and repair any errors you found here).  ... View more

I see this error occasionally when the attribute table I am trying to open has another table joined to it. I am usually able to fix this by removing the join and creating it again. If that doesn't work, I've also had luck closing the project and opening it again. ... View more

The XY to Point tool is looking for columns with the field type of "double." It seems like your customer lat/longs aren't being read in by ArcGIS Pro as "double." Sometimes that happens if you have a value like "NULL" or "N/A" in your list of coordinates - to accomodate for the text value, ArcGIS will convert the entire column to text. If you confirm that your customer lat/long fields don't have any text in them but you're still unable to see those fields in the XY to Point tool, you can save your excel sheet as a .csv file and create a schema file to go with it. In Notepad or whatever text editor you use, save a blank document with the filename "schema.ini" in the same location as your .csv file. Then in your text editor, you will need to specify a) the name of the .csv file in brackets, b) the format of the .csv file, and c) the field names and what type they should be. Like this:  [YOUR CSV NAME HERE.csv] Format=CSVDelimited Col5=Customer_Latitude Double Col6=Customer_Long Double Of course you'll want to replace "YOUR CSV NAME HERE" with the name of your CSV file, and double check that the column names I used match your column names. Back in Pro, use the .csv file as your input for the XY to Point tool. Your customer lat/long fields should show up now. As for your question of "Am I using the right tool?" - if you're trying to make a layer for customer points and a layer for distributor points, then I would split your spreadsheet into two separate files and run the XY to Point tool on each file. You can add a unique ID field before you split the data so you can join them back together if needed. If the distributor and customer that share a row are related and you'd like to see how they connect, you can use the XY to Line tool. That tool will ask you for four inputs instead of two - a lat and long for the start and ending of the line (in your case, the distributor lat/long and the customer lat/long). I hope this helps! Let me know if I misunderstood your question. ... View more

Robert Jensen,  Now that this post is a few months old, is there a more specific ETA for when we can expect BFUSA to be integrated into the world geocoder? Or a roadmap for when it will be available in the Living Atlas, basemaps, training datasets, etc.? Thanks for any update you can provide! -Kelly ... View more

Praveen, Thank you for the update! I really appreciate it. -Kelly ... View more