Latest Contributions by MDB_GIS

I know the update was successful because I can see the symbology changes that I made in the map. I can also see the new feature class that was added to the service on the REST service page. I made sure that the Layer IDs were correct and not conflicting before publishing so I know that there is no issue there. Any ideas on how to get the layer to show up? A few screenshots below:   An additional test was I just republished a test layer from scratch containing all 8 layers. When done that way, it shows up as expected with correct symbology. Using this is not ideal, however, as we have numerous maps and applications that are dependent upon this service so I really do not want to have to go and reconfigure every single map that utilizes these layers.          ... View more

I have created a zoning viewer that I want to be searchable by parcel number. In the instant app, I have the search configured as follows:  If I use the search field, however, it does appear to search the layers as it auto suggests a few parcels, but it suggests parcels that don't make sense. For instance, if I search 'B 02' it will show the following suggestions: These are all valid options and it will zoom to them as expected.  However, I am trying to search for parcel 'B 02  041.'  It will never show up as a suggestion, however, no matter how much you type. In the screenshot below, you will see that I have entered the full parcel number in the search box, but it does not suggest it. Despite the parcel literally being on the screen (red parcel highlighted in blue).    To further complicate this, the search works just fine in the web map that is powering the instant app. See below:    I've been trying to figure out what is causing this for several hours to no avail so I would greatly appreciate any advice!     ... View more

I maintain addressing data for our county and we have to maintain the data in two standards. The 'new' NENA 911 standard, and the old legacy standard that works with our 911 CAD system. The fundamental difference between the two is that the new standard fully spells everything out and is in proper case whereas the old CAD standard uses abbreviations and is in all caps. So for instance: Road = RD Street = St Alley = ALLEY Bend = BEND I would like to set it up so that when I populate the 'New' standard's field, it automatically translates that to the correct value for the old standard. The challenge with this is that there are over 100 possible values, and thus more than 100 translations that would need to occur. I was considering two ways. The first was an attribute rule with a very long if/else statement that translated everything. I haven't tried this yet mostly because of the tediousness of writing it as well as concerns about the performance impact of such a long attribute calculation. The second was with conditional values. I've actually been testing this but I keep getting an error.  I have a field group set up that contains both fields. I have Bend and BEND paired, but for some reason, when I actually edit the field to assign the "Bend" domain, I get an error message on the attribute window saying:   This doesn't make sense, however, because as you can see, it IS a member of that domain.  Probably something that I'm not understanding but I have yet to get it to work correctly. All that being said, I'm hoping someone here can tell me the easiest way to accomplish this.    ... View more

I am trying to write an attribute rule that compares a parcel's calculated area to the stated (deeded area) and if it is off by more than 10% of the total acreage to flag an attribute field for it. This rule does that:   //If the absolute value of error acres is greater than 10% of the stated acres, then report mismatch. Otherwise, report that it is acceptable. var QAQC_Eval = iif(abs($feature.ERROR_ACRES) > ($feature.StatedArea * 0.10), "Acreage mismatch. Deeded acres and calculated acres do not fall within OCGIS tolerance.", "Acreage ok. Deeded acres and calculated acres fall within OCGIS tolerance.") return QAQC_Eval;   The problem I am having is that there are sometimes exceptions where I need to be able to manually clear the flag and mark it as an exception (like in cases where I have looked at the issue but can't correct it due to insufficient information or some other problem).  I would have thought that if I had checked the "Editable" box in the attribute rule configuration, that this would allow me to manually change this value if required. Unfortunately, that doesn't seem to be the case because when I manually change that field, I get an error message saying "Edit Operation failed - no edits producing database changes were found." Here is the current rule configuration panel: Ideally, this rule will only fire off if the geometry is changed, which is why I only have the "Shape" field set to active. Would really appreciate some help with this as this could really improve the QAQC process for our parcel data!   ... View more