Latest Contributions by KimberlyGarbade

A few ideas... keeping in mind I didn't say good ideas... The parcels might be mutli-part. Less likely, the parcels may be related to another table, or might have been created from a dataset that was. For example parcel data is often linked to CAMA data, a series of relationships could do it. If you select by attribute on 37 Broad St? How many parcels are returned?  Then try selecting by attribute on the RE assigned to that parcel or the owner.  If only one parcel comes back I'm wrong.  ... View more

I did test in a file GDB. I'm also using 2.8.5 (had to downgrade... long story).  Hope it works out for you since I really wanted to solve this one but I found nothing to solve and I hate mysteries.  One last hail marry might be I notice your feature class name in the FeaturesetByName function is not fully qualified. By that I mean it's usually databasename.dataowner.featureclassname. but in the code above I just see dataowner.featureclassname. try fully qualifying it by adding the database name. Since I tested in a file GDB I didn't have to do that so maybe that's why it worked. Maybe....but your code tests for null sets and values so.... ... View more

I have tried it and I can't get it to work.  I hope I'm missing something simple and that I'm wrong here, but I think the problem is that we are assuming that Intersection is going to return a geometry of type point and I'm not sure from the documentation that it does. The only work around I can think of is to return the path from $feature using something like this: var pipeGeom = geometry($feature) var paths = pipeGeom.paths Then step through each point (vertice) in the "path" to determine if it intersects a pipe other than $feature.  By this I mean you'll have to do something like this to make sure you don't consider the pipe you are currently entering; because of course all the points on that pipe's "path" will be intersected: var thisPipe = $feature.GlobalID var pipe = Filter(FeatureSetByName($datastore, "pipe"),'GlobalID <> @thisPipe')  When/if you find the point/vertice along the path that intersects another pipe, that will be the geometry you use to "edit:" your point layer. Again, I hope I am wrong and that I'm missing something simple, but the Arcade documentation for Intersection doesn't mention "if you provide two line geometries as inputs a set of intersection points will be returned".... ... View more

You know.... I used your code (had to change some names of course) on some sample data and it works like a charm.  I've tried to break it by disabling the script from running on "Update" (which at first I thought was the problem - its not) and by setting "Exclude from application evaluation" (even though not sure it would matter in this case) and it just keeps working.  The one time it didn't work was when I had an error in the polygon geometry I was splitting.... So maybe your problem isn't the script but the data it uses. As an FYI and probably apropos of nothing:   I didn't set a variable named "intersecting_field" so, for example, my script used "return '51'+intersected_feature.FIPS;"... but like I said, can't see why that would make any difference at all. ... View more

Can you give me an example of what you mean by "I need to match the data by its field rather than by its name"? ... View more

That does look close from what  I can see.  Try making "BufferValue" a precondition of the "Select Layer By Location" tool.  That way it has to exist before that tool will try to run.  That being said, from your earlier description it does sound like you need an iterator to step through your address points (if you want to process them one at a time and all (or a selected set of them) at one time).  You could just select one address point for testing before adding the iterator.    ... View more

No problem.  I'm glad it worked out. ... View more

Has the connection worked recently and absolutely no changes have happened to you software versions since? If your Oracle version was just recently updated from 12c to 19c it could be a comparability/software version problem. Check out your current desktop (either Pro or ArcGIS desktop) version, and the version used to create or update your geodatabase.   https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/example-finding-the-geodatabase-release.htm Then look up compatability. You might need to upgrade your EGDB.   It could also be that your SDK version is no longer compatible with your desktop or Oracle version. I'd start there.  ... View more

That could be for a few reasons, but in this case I think it's because this is a .csv file. I would export the csv file to a table in a file geodatabase and add the field there. I guess you could also open the .csv file in Excel and add the column and perform the right function there (excel has its own Right function). Then re-add the .csv to your project. Keeping in mind that a .csv cannot be open in one program and edited in another at the same time  it will be locked, which could be your problem now   ... View more

Sounds like you want to use the "Get Field Value" utility.  You'll find it under Utilities dropdown in the Insert Group of the ModelBuilder tab (highlighted in both images below).     Once you pick the field you want to get the value from (in your case your buffer attribute field), you can reference that value in another statement using the %variable% syntax (in the below case %Value%). Hope I'm understanding what you want correctly and that this helps. ... View more

That's kind of big question.  Projections take the not so round earth and project it onto a flat surface.  Some projections keep measurements/distance more accurate at the cost that the shape of represented areas my change slightly (especially larger ones).  Other projections keep the shapes of areas more accurate than others at the cost of distorting distance measurements.  Other projects preserve direction or angles or scale, so  the one you choose should be based on what's the most important aspect of the data for your purpose.  Coordinate systems are too much to talk about, but here's a good link though:  https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/coordinate-systems-difference/  ... View more

When you say it doesn't work do you mean it generates an error, it doesn't return a value, or it returns an unexpected value?  When I test the code, it returns a value, just not the one I expected.  For example I enter "ST1" and "Moderate frost risk" into the function and get "Frost free" when I would expect to get "Low frost risk".  The reason for this is elif is exiting the function when it find the first match for 'ST1' in FIRST_KOPP (I.E. the first elif in the function) so it never makes it second elif to return 'Low frost risk".  Is this the behavior you are referring  to? ... View more

Sounds to me like you'll want to set up a relationship class between the buildings and the streets.  For that to work you need a foreign key in your buildings layer that is the ID of the street it is related to.   ... View more