I'm trying to setup a standalone pelias server and have a pelias-webview ( running master ) working with geonames import, and have pointed a pelias-demo angular app at the host. The requests go through, but /suggest request cause the following error:

TypeError: Cannot call method 'split' of undefined
at buildSuggestCommand (/var/www/mapzen/pelias-webview/controller/suggestController.js:50:40)
at module.exports (/var/www/mapzen/pelias-webview/controller/suggestController.js:15:11)
at callbacks (/var/www/mapzen/pelias-webview/node_modules/express/lib/router/index.js:164:37)
at param (/var/www/mapzen/pelias-webview/node_modules/express/lib/router/index.js:138:11)
at pass (/var/www/mapzen/pelias-webview/node_modules/express/lib/router/index.js:145:5)
at Router._dispatch (/var/www/mapzen/pelias-webview/node_modules/express/lib/router/index.js:173:5)
at Object.router (/var/www/mapzen/pelias-webview/node_modules/express/lib/router/index.js:33:10)
at next (/var/www/mapzen/pelias-webview/node_modules/express/node_modules/connect/lib/proto.js:174:15)
at Object.handle (/var/www/mapzen/pelias-webview/app.js:23:5)
at next (/var/www/mapzen/pelias-webview/node_modules/express/node_modules/connect/lib/proto.js:174:15)

After the traceback, when I actually hit return in the app and hit the /search endpoint, I can see that the request is made ( by inspecting XHR responses ) but the UI no longer updates.

Thoughts?

What's the fate of this demo? We should at a minimum get a tangram basemap in there. We could kill the demo for now and have it point to the search project page.

Thoughts?

From javascript point of view, we have:

new handler window.ondevicemotion
new event object:

event.accelerationGravity, with x, y, z attributes
event.accelerationIncludingGravity, with x, y, z attributes
event.rotationRate, with alpha, beta, gamma attributes

window.ondevicemotion = function(event) {  
    var accelerationX = event.accelerationIncludingGravity.x;  
    var accelerationY = event.accelerationIncludingGravity.y;  
    var accelerationZ = event.accelerationIncludingGravity.z;  
}  

Lets try and use this information to display the 3D aspect of the map on mobile browsers better - so that when you tilt your phone you can inspect the 3D building better.. That would be so cool, wouldn't it?

See here:

You can fix this with a z-index of whatever on the #searchbar element:

The height of the search bar is odd, though...

It would be nice if the map automatically opened up on your current location, once the geolocation dialog has been approved once it should always do this without prompting the user again.

when typing non-english languages, character accents are removed. Most probably due to the toLowerCase method in javascript.

ie. search Cinématte, query string will say cinematte.

due to a related bug this can cause the same query to result 0 results.

Some people have asked to bring back the pin layers.

Eg. turn on all geoname pins nearby.

cc/ @rwelty1889

This may only affect lon, when you scroll to the right past New Zealand the lon value in the URL bar continues to rise and rise, eg 1468.13:

https://mapzen.com/pelias#loc=4,14.60,1468.13

This causes Pelias to throw 400 (Bad Request) errors.

It would be nice to spend some time styling the design of the demo to be more UI/UX friendly.

This layout looks nice & clean:

src: http://nerds.airbnb.com/mapping-world/

cc/ @hkrishna @souperneon

the old dash had a great feature to 'jump to' locations in the world and had a button to jump to your current location.

these are really helpful for anyone who doesn't live in NYC

There is an intermittent issue with rawgit which is preventing the demo from showing

an exciting list of cities, but San Francisco needs to be on there too. Ideally #15/37.7853/-122.3962

Not sure if this is the right place for this issue...

If you view mapzen.com/pelias on your mobile phone you get a nice responsive menu with a menu toggle button.

For some reason this menu button will toggle the menu open but not closed again.

Seems to only affect the pelias demo page...

I have a location that has 2 points: a geoname & osmway. I was trying to see why sometimes it only returned 1 result & sometimes both (something to do with zoom & bbox?). While playing around, I found that sometimes it wouldn't remove the primary result from the list of possibilities. What's more interesting, it suggested the option that was a little further away. I know the url isn't RESTful so you won't get the same result, but here are the findings: https://cdn.rawgit.com/pelias/demo/3way-toggle/index.html#loc=4,43.29,-127.49&q=North Medford High&t=fine&gb=bbox