Public facing Geoform, private data

[JasonPoser1]

Being new to Geoform and from a 10000 foot level perspective we are looking for a user side (map + form) solution to gather requests for service based on a physical location. Preliminarily the user submitted map location would only be used as a point of reference and discussion internally. The map location would present us with a common operating picture to follow up with the person who submitted the request and discuss it.

The two issues that we do not have a clear understanding are basically: 

1. How can the form allow the pubic to submit a request with out exposing all the other requests to other public users. For example the public facing map shouldn't expose all the other requests for service on it.

2. Is there a method to authenticate or otherwise deter false form submissions. We question if a public facing Geoform will create an situation where we will not be able to easily distinguish and follow up with valid submissions vs fake and false submissions.

Any thoughts?

[RandyKreuziger]

I've got the same question.  Anyone have solutions?

[MatthewLofgren]

Regarding the first question. If your map/feature service is coming from ArcGIS Server, you can set the 'Maximum Number of Records Returned by Server' to 0. So your form will take in submissions but will not show anything on the map.

If you were in Server Manager -> Edit your service -> Parameters tab -> under Properties

[AdrianaPaese]

Setting the 'Maximum Number of Records Returned by Server' to 0 may work.

However, as your service needs to be public in order to use the GeoForm template, data is exposed in ArcGIS Online

Another approach, I believe, would be to secure your ArcGIS Server service and use a resource proxy....

[SimonJackson]

Is this not a case for making use of Application Authentication?

See this post for more info.

[AnjoletteSpradling]

Re #1:  I've used the directions found here​ to remove some fields from public view but I can't see a way to filter requests by users based on who's viewing the map since there is no sign-in. The Citizen Service Request template or something similar may offer that option.

Re #2: Probably not. Depends on what you need to verify. You could require name, phone and address but users could still submit false info. Without having them create a log-in, if you had access to some verified database (like utility bill), you could require an account number and cross check with that to verify contact info. How do you know there is really a pothole where they said? Someone has to go check.

[JenniferStone]

I know this is a bit late to the game but I felt it worth adding for the next head scratcher to come along. I had a similar problem. I created a Special Needs Registry geoform where the public can submit a special needs registration using form and map. That form includes fields with what some users might consider "private" information (i.e.: name, address, medical conditions, etc...).

The problem I was running into was that the geoform requires the pop-up in order to know what fields to provide but I didn't want existing submissions to be seen by those using the app nor did I want them to be able to click on a point and see the details of any prior submissions. What I ended up doing was going into the web map and creating a filter of 'ObjectID is blank' on the SpecialNeedsRegistrant layer (for you it would be whatever layer you are basing your form off of). This filters out any features that have an ObjectID (AKA - all of them) but still allows the pop-up to provide the form fields.