Latest Contributions by RichardHughes2

Raluca, This morning I drew up a proof for solving the Z-value of a point with a known x, y on a plane defined by three vertexes with x, y, z.  This seems like a calculation that would already be in the api, but if it is not can it be added? ... View more

Hi Raluca, You are correct in that when I say surface I am referring to airspace surface.  Those are sloped polygons.  These polygons have z-values defined at each vertex.  They are rendered using absolute-height.  In my local scene we are extruding a point to a height chosen by the user, and the penetration is visible in the app.  I would like to programmatically filter polygons that don't intersect.  There can be a lot of polygons you see. and some of the polygon surfaces have steeper slopes than others.  Right now every polygon that interects in 2d space is visible and is returned from the IdentifyTask.  I was unable to get the Query Task to work on the map service.  It seems to only accept layers within the map service by appending the layer index to the url.  That could also be clarified a bit more in the API.  We have many layers in the map service so I am using the IdentifyTask, eventhough the documentation states that it is not supported in a Scene View.  To perform the geometry comparison I am creating a polyline with the base and peak elevation of the obstacle with a one foot offset at the peak on the X and Y coordinates to prevent a completely vertical line.  I have been building Queries and executing them on the feature layers in the app with this geometry and it does not work in 3d.  Actually calculating the penetration, or vertical distance the obstacle protrudes through the surface, is what we rely on the rasters for.  In a completely separate workflow we are generating rasters from the 3d polygons by going polygon->multipatch->raster.  Using an Identify Task on the rasters in a map service with a point geometry returns the pixel value for each raster at that location.  What I want to do in the Scene View is filter out the polygons (surfaces) that don't intersect the obstacle, or are outside a specified vertical clearance at the location of the obstacle without having to query the rasters.     I guess I will need to to a Geoprocessing Service to get the job done, yes?  Building and using rasters with a 5x5 ft cell size for the app is outdated when a geometric intersect comparison is all we need.    I uploaded a video attachment demoing the app functionality.  it is in development ... View more

Hi Raluca, Thank you for pointing that out with the 2d geometries for the Geometry Engine.  Seeing the Geodesic Buffers 3D kept pulling me towards the impossible. What we are doing is showing penetrations in an airspace application.  We want to identify what 3d surfaces are intersected by a vertical line representing an obstacle.  We can see the intersection in the Scene, and we measuring them.  The rasters in the map service are not being added to the app.  They are being queried through an Identify Task (which is not supported in the Scene View) and the pixel values are used to calculate the differences in elevation between the surfaces at the specified point.  Does that make sense?  The data is then shown in a table in the app. The need to create the rasters for calculating the difference in elevation is all they are for.  The rasters are not visible in the Scene and are not used to create a layer, the url is used in an IdentifyTask.   We would like to be able to determine whether a vertical obstacle intersects a 3d polygon. ... View more

Hi Kristian, That is interesting.  The API documentation does not really specify that so cut and dry.  Also, the Identify Task is stated as not supported on 3d Scene Views.  Turns out that because the geometry operations are not working on 3d data, we are using the Identify Task to query pixel values from rasters on a map service to get the differences in elevation between features.  I understand that the extent of the Scene View could causes issues, but when Identifying by a point it works.  What does "Not supported" mean in the context of the javascript api?    It would be nice to not have to generate rasters to calculate differences in elevation to determine if a feature intersects another.  The Geometry Engine, based on the API seems like the correct solution.  Is it that a Geometry Service is required instead so ArcServer can perform the intersect comparison?   Thanks, Rich ... View more

Hi Kelly, That Early Adopter AGOL site is blocking my access because I am not an esri employee. Just to be clear regarding my question.  I am using the Unique Value Renderer, and want to pass Legend Layers into the Print Task for AGOL.  My Question:  Do I need to be more detailed about building the renderer for the LegendLayers so that AGOL print task will honor it, or is it a waste of time because the PrintTask will always show Override1, Override 2, etc?  Currently, the renderer is being retrieved from a LayerView on AGOL and applied to the layer in the map.  My next approach is to build a new renderer after retrieving the json and adding the types with a label one by one, but I don't know if that will resolve the Override issue.  It is simply that I need to have a label next to the color for the type in the legend.  The colors are there but the label always says Override.   I will be testing with building the LegendLayer renderer again today. ... View more

Hi Kelly, I missed the Dev Summit this year, or else I would have an answer.  Right now I am the AGOL print service and find that the legend items only work when the web map and its layers are not altered in any way.  After publishing.  I am thinking that that if the feature layer definition does not match the original service definition, then the AGOL print service won't render the label.   You mentioned in the previous comment that a solution is in the works for a future AGOL update.  For me, in a situation where we are deploying apps now, do you have any api documentation on how best I should work with the current AGOL legend for Feature Layer and Feature Layer Views?  It seems that Feature Layers Views are not supported, but Feature Layers are if they are not modified after publishing to AGOL.  I am at a crossroads where I should either render my own and it too the MAP ONLY print along with the log and North arrow I am adding, or use the AGOL Legend. Thanks, Rich ... View more

What I've found is that python None, True, and False values are automatically substituted for the null, true, and false values returned by the service definition.  Before submitting the post data I have to dump the data to a json string, then replace these python types with the associated json type.  Both are specified as strings since I am replacing the text in the json string.   Other cleanup needed is to remove all single apostrophes from domain descriptions. ... View more

Asrujit, I did contact Tech Support who reached out to the Dev team who stated that it will be supported in a future release but where unable to say which one.  Thank you for your guidance on this topic. ... View more

I've been looking through all of the online docs and don't seem to be able to either support or reject your statement about a Desktop gdb.  Does creating a replica using the Database Server on SQL Express require the enable enterprise geodatabase with a keycodes files?   ... View more

Asrujit, We are building a geodatabase that holds master data in a dozen feature datasets.  We are building a workflow for publishing to AGOL for Collector and are planning on implementing global ids to bring the data back into the master.  ArcServer is not part of our available software now so my two choices are file geodatabase or database server.  Neither of these will be able to be a parent in a replica or a version tree correct?   Thanks, Rich ... View more