Latest Contributions by MathewSuran

That looks pretty cool.  Thanks for the resource! ... View more

Sorry for the delay, just getting back on this.  So if I don't need the relationship class in the gdb, then would I have to load both feature services and just not display one? ... View more

I think I made some progress with this example: Query and edit related records | ArcGIS API for JavaScript It has the on click event we were looking for "incidentLayer.on("click", function(evt) {" along with the relationship query I am looking for I think.  This creates a popup with the query results instead of the graph that I want, which shouldnt be too hard to figure out. I am going to try to piece this together and see if I have any luck. ... View more

By a simple mouse click at the location. ... View more

Thanks.  Just to clarify, did you create a relationship class in your gdb?  How do you have your data set up? ... View more

I have a similar field for both line and point features that specifies the location.  The similar field will only be used for location purposes.  When the line is selected, I want to display (in the form of a graph) the points elevation (Field name=Z) that relate to the same location of the line.  The line is basically the template for where the points should be taken.  Since displaying the location of the points is not important here, this is why I want to just display the line and have all of the points elevation data be referenced when it is selected. I am looking for the best way to set this up in the gdb I am pulling the features from.  Whether it is creating a relationship class or what Sapna suggested above. No need for the attribute inspector or infowindow, since the elevation data will be automatically populated in the line graph. ... View more

I totally agree.  Thanks! ... View more

That is actually exactly what I am looking for, great find! Would you suggest utilizing the data store over a query for this application? I may be completely off here but it seems like the query would be pointless to incorporate and the data store with the combo box is the way to go. Not to get off topic for this thread, check out my other thread I started for setting up the data that I will be using for this webapp.  Any suggestions there would be appreciated. Combine line and point feature classes attributes ... View more

Thanks for all of that.  I want to be able to select a feature (line) and then apply a query to the selected feature.  I thought of check boxes with all of the years and spring/fall but that would be too space hungry, so I thought that 2 text boxes to fill in would be easiest.  In the first box, enter the year.  In the second box, enter either fall or spring.  Those are the 2 attributes I want to query to populate the line graph. As far as adding multiple lines, I want to be able to do the above process total 2-3 times, depending on how cluttered the graph looks.  I can manually give values for each line to populate multiple, but haven't tried the above example since they tie into each other. Is there a way to reset the query if you want to display new attributes?  I was thinking of turning the symbol in the graph legend into a movable and deletable object.  Movable so you can rearrange the order of the lines and deletable to add a new query/line. ... View more

Hey William, Yes I am still working on this.  I figured out how to add the suggestion from Kelly into my webapp.  The only problem is that her example only utilizes one feature layer and one query.  I am currently working on trying to add multiple steps to the query to add multiple lines to the graph. For example: Selecting a feature opens a text box to type in a year then type in spring or fall.  This will then populate the line graph for those criteria.  I want to be able to do this up to 3 times for a max of 3 populated lines.  Hope this makes sense. I am open to suggestions though. ... View more

Ok, will try first thing tomorrow. ... View more

Thanks for that.  How would I reference this view to plug-in to my webapp? ... View more

Yes, there is a common field name that Identifies the location of both features named "Line".  There is 1 line per location while there are many points around the line, not directly on it. ... View more