- sjpdAsked on September 20, 2015 at 11:21 AM
I'd like to use the address map locator widget in a surveillance camera registration form. It will help pinpoint the addresses and validate that they can be properly geocoded. But there are some design issues with the widget.
1.) I'd like to be able to map the address components (address, city state/province zip, country) to discrete fields in the database, but the widget sends them all as one string, delimited by linefeeds, to a single column. Specifically, I need the Lat. and Long. as separate fields.2.) The widget now puts my "County" (example: Santa Clara) in the Province field. This changed a few weeks ago when the widget was modified and updated to fix a different bug related to dragging the pin to a new location. The "State" (Example: California) should fill the Province field for US addresses.3.) It would be nice if the widget could act as an address field in the same way as the standard address field works, so that a map is displayed when viewing submissions.4.) It would be helpful if valid Country, State and City could be defined for the form so the widget would display an error message if a location outside my pre-defined valid City were entered. Something like, "Only addresses in San Jose are allowed in this form".5.) Zoom level - It would also be helpful if the form designer had a parameter that sets the default zoom level for the map that displays in the widget. I'd like it to zoom in to level 11 or so, (Google zoom level z=11).
Here's my mapping form...
As a work around for the widgets deficiencies mentioned above, I created a second Address field where I ask the user to re-enter the address the Widget has already mapped. I did this to allow for Apartment numbers, and to ensure that the discrete address parts are available in separate columns. But it's a kludge and I'd like to make the form easier to fill out for the user by eliminating this extra address field.
We are exporting the data to a third party mapping database and do not have back-end access to parse the single address field created by the widget, to split the values. So it will be a great benefit if the widget can be modified in the ways I've mentioned.
I tried copying the entire form source code to host it on my webserver so that I can use my own client-side scripting to copy the widget address values into separate hidden fields, but it seems that cross site scripting security prevents me from reading the values in the widget and writing them to hidden fields when the widget is hosted on a different domain than the form.
So I need your help to improve a good widget and make it great.
- JotForm Supportashwin_dAnswered on September 21, 2015 at 02:58 AM
There seems to be too many feature request related to "Address Map Locator" widget. Let me try to understand and address the issue one by one. I will go ahead and create separate threads for your other questions and send feature request to our back end team.
1.) I'd like to be able to map the address components (address, city state/province zip, country) to discrete fields in the database, but the widget sends them all as one string, delimited by linefeeds, to a single column. Specifically, I need the Lat. and Long. as separate fields.
Yes that is correct. The widget send all the captured address data in one column of submission page. I am not sure if it is possible to send it in multiple columns of submission page. When you say "database", are you actually saving the form's data in your own database? If yes then it is possible to separate the data of the address map locator widget in your own page. The widgets send the data in json format and you should be able to split it and save it in multiple columns of your own database.
#2. You will be answered in the following thread: http://www.jotform.com/answers/666611
#3. You will be answered in the following thread: http://www.jotform.com/answers/666612
#4. You will be answered in the following thread: http://www.jotform.com/answers/666613
#5. You will be answered in the following thread: http://www.jotform.com/answers/666614
- sjpdAnswered on September 21, 2015 at 01:44 PM
Thank you for your reply Ashwin,
We are sending the CSV file to our vendor, who then import the data into their database.
I don't have control over that process and they've requested the data to be in separate columns.
So asking them to parse the widget data that appears in a single column, into separate fields is beyond my control, and represents a technology hurdle that is out of scope for my project and statement of work from the vendor.
It makes me wonder why the Jotform widget designer elected to put these mapped address data into a single column with linefeeds as delimiters. It's inconsistent with most or all of the other form fields that I've experienced at Jotform. And as a usability issue, it seems a bit obtuse and inefficient. I hope constructive criticism is welcome... ;-)
- JotForm SupportMikeAnswered on September 21, 2015 at 05:19 PM
We have sent a ticket about submission data representation of the Address Map Locator widget to our developers for consideration. However, there is also a chance that widgets are limited to one column per widget.
We will let you know if we have any updates on this.