Selecting feature to be used in workflow
Is it possible for a user to select a point feature, and for the attributes of this point feature to then be used for further use in a workflow?
I have a point layer which contains contains address', and I would like the user to be able to click on the point which represents their address, which will then be used in a workflow to find their nearest facilities. I currently have a find my neast set up where the user can click on the map and then it will find their nearest facility, but I would like to restrict the user to only be able to select the address points. The reason I want to do this is that I have an idea use this selected address to push out into a route finding website.
I have all find my nearest/route finding cracked, but only using the lat/longs of the users clicked location and the lat long of the nearest point. I find that the actual locations of the lat longs are not very acurate (due to us using British National Grid), but to use x y locations, I have to stick with WGS, as Google directions will not accept BNG. Because of this, it would be ideal to be able to use the address (which is already in the attribute table).
Hope that makes sense!
-
Aled,
Is the user selecting the point feature as part of the workflow, or are you looking to have the user select a point a feature first and then run a workflow that uses its attributes?
0 -
Hi John,
I suppose it does not really matter whether it is part of the workflow or not. A the the moment it is part of the workflow, so the user selects the find My Nearest option, then the workflow starts by asking the user to select their location. Provided I could get it to work, I would be happy enough for the attributes to be used in the workflow instead though.
Thanks.
Aled
0 -
So if I understand correctly, right now the workflow works off of the location the user clicks on, but you want to make the user select an address point instead?
As for the routing website, do you need to pass the address or the lat/long associated with the address to the service?
0 -
Hi John,
Sorry for the late reply, annaul leave and other work have been taking up my time. You are right that (currently) the workflow works off the location the user clicks on, but I would like to change it so that the user has to select a point address instead. With regards to the routing website, I need to pass the address of the point (which is held in the attribute table) to the service.
In an ideal world, it would be fine to pass on the Lat/Long of the point, which would also allow me to keep the workflow as it is (as the user clicking the point would work fine that way) but I am having some offset issues with the transformations between British National Grid and WGS 84. This means that when the users clicks the point, the lat/long coords are in the wrong location, so if I could pass the address information of the point it would work around this issue.
0 -
Well, you could use a combination of Display Capture Geometry and Query Task activities to get at the attributes in the address point. Another way to do it would be to launch the workflow from the feature by using the RunWorkflowWithArguments command in the feature long description link. That way the workflow would be tied to the specific address point, and you could use either the address or the lat/long (i.e. geometry extent) of the feature.
For example, I run a mailing labels tool from both parcel polygons and points by passing the parcel ID (PID_NO).
link syntax: "command:RunWorkflowWithArguments?workflowid=Create_Mailing_Labels_hyperlink&pid={PID_NO}"
pid is an argument in the Create_Mailing_Labels workflow that is used in a Query Task activity to select the associated parcel and run the workflow against it.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
5 kommentarer