Latest Contributions by ChrisBuscaglia

Thanks for all the comments on this issue, we've logged it as an enhancement. Thanks, Chris ... View more

Angelo -  Did this resolve the issue? Thanks Chris ... View more

Angelo, I think that you uncovered a bug, the widget may be looking for a camelcase "RelateGuid" field in the lines layer - instead, Oracle DB is changing it to be relateguid - all lowercase.  Using the AGO Assistant - you can manually change the name of the field in the application json. ArcGIS Online Assistant  Data Section -  "relatedGUID": { "name": "RelateGuid", "type": "esriFieldTypeGUID", "alias": "RelateGuid", "length": 38, "editable": true, "nullable": true }, ... View more

Can you please send me a screenshot of your rest endpoint showing the fields as shown above?  What DBMS are you using, oracle? ... View more

Yes, this is strange - does the line feature layer have a relateGUID field? OBJECTID (type: esriFieldTypeOID, alias: OBJECTID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false) Bearing (type: esriFieldTypeDouble, alias: Bearing, SQL Type: sqlTypeOther, nullable: true, editable: true) Distance (type: esriFieldTypeDouble, alias: Distance, SQL Type: sqlTypeOther, nullable: true, editable: true) Radius (type: esriFieldTypeDouble, alias: Radius, SQL Type: sqlTypeOther, nullable: true, editable: true) ArcLength (type: esriFieldTypeDouble, alias: ArcLength, SQL Type: sqlTypeOther, nullable: true, editable: true) ChordLength (type: esriFieldTypeDouble, alias: ChordLength, SQL Type: sqlTypeOther, nullable: true, editable: true) SequenceID (type: esriFieldTypeInteger, alias: SequenceID, SQL Type: sqlTypeOther, nullable: true, editable: true) Category (type: esriFieldTypeInteger, alias: Category, SQL Type: sqlTypeOther, nullable: true, editable: true) RelateGuid (type: esriFieldTypeGUID, alias: RelateGuid, SQL Type: sqlTypeOther, length: 38, nullable: true, editable: true) Shape__Length (type: esriFieldTypeDouble, alias: Shape__Length, SQL Type: sqlTypeDouble, nullable: true, editable: false) ... View more

Angelo -  Thanks for posting - this error happens when you don't have the proper relationship between the parcels and lines feature layers used for the application.   Can you share the URL to the app? Thanks,  Chris Buscaglia Government Solutions ... View more

BPriya K‌ I'm not sure exactly, can you share some screenshots of your configuration panel? Chris Government Solutions Team ... View more

Hello Vanessa,  There could be a number of things wrong with the configuration. Please contact support so that we can triage it more effectively. One simple way to address this issue is to use our "one-click" deployment option, which will stand up the application in your environment ready to use. Install add-in - Parcel Drafter | ArcGIS Solutions for Local Government  Chris Government Solutions ... View more

Adam -  The layers that we provide include sales, foreclosures and appeals - they will have to derived from your tax and assessment system. The Tax Parcel layer is a hybrid - contains parcel geometries and assessment system information.  One simple way to get these attributes is to join the CAMA attributes by parcel number and then use the load data steps here.  You'll want to use the append approach. Load your data - Value Analysis Dashboard | ArcGIS Solutions for Local Government  If you would like to get on a quick call to go over this, please let me know. Thanks Chris Buscaglia  Local Government Solutions Team ... View more

Jefferson,  We don't support radial bearings/central angles - everything else is supported. - + Radius values have been the norm in ArcGIS desktop as our parcel maintenance solution uses that input style. We do have documentation for other shortcuts - like quadrant bearing (-1 for NE, -2 for SE, etc.). Create new parcel - Parcel Drafter | ArcGIS Solutions for Local Government  Hope the helps  -Chris ... View more

var QuadrantBearingFormat = true; //set as 'true' for quadrant bearing and false for north azimuth var direction=$feature.Bearing; var distance=$feature.Distance; var radius=$feature.Radius; var arclength=$feature.Arclength; var radius2=$feature.Radius var prefix; var postfix; var bearing; var quadbearing; var validValuesArray; var missingValuesArray; var degrees; var minutes; var seconds; var DMS; function NorthAzimuth2Quadbearing(azimuth){             if (azimuth<90 && azimuth>=0){                         bearing=azimuth;                         prefix = "N";                         postfix= "E";}             else if (azimuth<180 && azimuth>=90){                         bearing=180-azimuth;                         prefix = "S";                         postfix= "E";}             else if (azimuth<270 && azimuth>=180){                         bearing=abs(180-azimuth);                         prefix = "S";                         postfix= "W";}             else if (azimuth<360 && azimuth>=270){                         bearing=360-azimuth;                         prefix = "N";                         postfix= "W";}                        degrees=floor(bearing);             minutes=floor((bearing-degrees)*60)             seconds=((bearing-degrees-minutes/60)*3600)             if (seconds>=59.5){                 seconds=0;                 minutes+=1;                 if (minutes==60){                     minutes=0;                     degrees+=1;}}             quadbearing=prefix+degrees+"°"+text(minutes,"00")+"'"+text(seconds,"00")+"''"+postfix;             return quadbearing; } function DMS(bearing){     degrees=floor(bearing);     minutes=floor((bearing-degrees)*60)     seconds=((bearing-degrees-minutes/60)*3600)     if (seconds>=59.5){         seconds=0;         minutes+=1;         if (minutes==60){             minutes=0;             degrees+=1;}}     DMS=prefix+degrees+"°"+text(minutes,"00")+"'"+text(seconds,"00")+"''"+postfix;     return DMS; } if (IsEmpty(direction)==false) {  //if direction exists             if (IsEmpty(radius)==true) {  // if radius is not populated  --> it is a straight line                 if (QuadrantBearingFormat==true) {  //using quadrant bearing format                     return NorthAzimuth2Quadbearing(direction) +'  '+ text(round(distance,2));                 }                 else {  //using north azimuth format                     return DMS(direction) + '  ' + text(round(distance,2));                 }                           }             else {    //radius is populated  --> it is a curve                 if (radius>0) {   // if radius is positive  --> right                     return  "R=" + text(radius) + text(arclength);                 }                 else {           // if radius is negative  --> left                     return  "R=" + text(abs(radius)) + text(arclength);                                    }             } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Try this - looks like Arcade isn't an option in the dropdown Adrian Welsh‌ I simplified the code a bit (Above) ... View more

Adrian Welsh‌  Please try this to complete the Bearing/Distance issue that you were having. Modify the custom label expression for the lines label in the webmap to have the following code. CBuscaglia-esristaff wrote: Hi Jefferson,    The feedback your team has given has been great, and we probably need to add some additional documentation in a couple areas.   For some reason, the screenshot from (deed plotter?) didn't come through, but maybe the following helps out?   To enter a chord bearing - please enter the chord bearing into the bearing field in the grid. To enter tangent curves, type *tb in the Bearing text box, or * to make the next line the same bearing as the previous.      Also, I'm working on a label expression for you that will display the bearings as you suggest, I'll keep you posted.   Chris This will make the label appear like this, even better...you can add the same code to the popup for the lines and it will appear in the table for the lines layer (like a new field). ... View more

Hi Jefferson,  The feedback your team has given has been great, and we probably need to add some additional documentation in a couple areas. For some reason, the screenshot from (deed plotter?) didn't come through, but maybe the following helps out? To enter a chord bearing - please enter the chord bearing into the bearing field in the grid. To enter tangent curves, type *tb in the Bearing text box, or * to make the next line the same bearing as the previous.  Also, I'm working on a label expression for you that will display the bearings as you suggest, I'll keep you posted. Chris ... View more

OK, thanks Kimberly - let me know if/when you run into this issue and we can run it to ground. Chris ... View more

Adrian, The sample application that we maintain uses State Plane coordinates and units, to make that work - you need to enter coords. if feet. For your application, the coords. need to be entered in meters.  For example, enter something like X = -9,818,344 Y = 5,122,119.  You can also use the coordinate widget to locate a start point and set the units to meters to test it out.  We did this so that you can enter (for example State Plane Coords.) in whatever units your coord. system is in without converting to Lat/Long.  Many states require coords. in state plane for platted subs. To change your application to use another coord. system, you can do that before you deploy - the parcel drafter layers will be set to that coordinate system, the basemap will remain in web mercator for this particular solution. Deployment options - ArcGIS Solutions Deployment Tool | ArcGIS Solutions  The data for angles is stored in the feature layer as doubles, so the Parcel Drafter can't add strings to that field.  I can look into a enhancement to also store string values in another field.  What exactly would you like to do with that data?  Knowing that may help me give you some guidance for a workaround/workflow that may satisfy the requirement. Chris ... View more