dianashk / batch-search-app Goto Github PK

I was getting an authentication error when I go to Start Processing -- after setting up all the fields and everything.

Turns out, I happened to choose an API key of mine that had been deleted (it shows "disabled" status on the internal admin page).

The app needs to show only currently active keys.

When I changed to an enabled key, the process worked fine!

one less step to get it on your own map via Tangram

If there is an existing output file with the same name, it will be overwritten without warning.

To reproduce:

1. Run the batch process once. This creates a file named output.csv.
2. Choose a different input csv from that same folder.
3. Run the batch process again. The contents of output.csv has been replaced with the new output rows.

Ideally, the user can set the output folder and filename.

• build in analytics about usage and each page
• add licensing info page (from menu?)
• add documentation (from menu?)
• support link (from menu and possibly bubbles throughout)
• add padding below all screens to allow scroll
• catch errors and don't show them on map (maybe separate log window)
• login is probably important to avoid stolen keys
  • already being done in Tangram Play (borrow code)
• add pricing and timing information
  • @souperneon will help with flow
• add all the filter params
  • boundary.country
  • boundary.circle
  • sources
  • layers
• get rid of stock menu
• update status bar icon
• add progress words to bar
• Change 'map columns' button to 'next'
• change 'ignore' to 'select' for dropdown in the mapping screen and ignore the columns users don't select

@souperneon

• change default window size
  • main window
  • auth window
• Add padding to tables
• Make table more narrow
• Icon for the app
• Work with select file screen
• Make a parent div and put all content of screens inside it- 80%
• Make text wrap when screensize is smaller
• Replace pngs for results

Displaying a large number of dots can cause Leaflet to stop updating, giving the appearance that the search tool has crashed, even though it is happily geocoding underneath the covers.

The appearance of dots are very exciting! So we should keep that as dynamic as possible, at least at the start.

A possible solution: above some threshold (say 500 results), display every 10th dot, and above 1000 only display every 20th or 100th dot or something reasonable.

give the user an opportunity to zoom into a city or region with a 'update bounding box` toggle

provide a checkbox to unlock the map -- while geocoding results for SF, I had a few results geocode to Null Island and could not zoom back to SF and see dots magically appear.

once the results are geocoded, upload the geojson and mapzen.js template to github (or S3 bucket?) so the results can be seen on a webpage, github.io or otherwise... and at least save the necessary files locally!

• add counter, ETA text, aka 245 of 85,402 results, 3.4 hours remaining
• for reverse geocoding, display live text results if possible?