The search box in the top left should bring up a bunch of autocomplete suggestions when you type stuff into it. Clicking on one brings up a place card view [1]. If my demo server falls over that will fail to populate. Once you have a place card you can hit "bike there" or something and then populate the "From" field that appears again in the top left to get a directions view [2]. Not ideal, the frontend was built in a few weeks by someone with very little frontend experience (me) so I did my best.
I guess it may be failing due to the request spike. Even otherwise, searching for common places like "San Francisco" or "New York" shows a dozen results all over Europe and South America, not the one place most people would be looking for. Street address search doesn't seem to work either.
Yeah, I've noticed that at least the way Pelias is configured in Headway, searches for administrative areas don't seem to work, like at all. I'm not sure if that's a config issue or an issue with Pelias though. Address search should definitely work as long as there's an appropriately tagged OSM node for your address, but the server's load average is 40 on a 6 core OVH box in Germany so you might have to be (very) patient to get anything back until the load drops to a level it can deal with.
Hi! Maintainer of Pelias here and co-founder of Geocode Earth where we continue to fund Pelias development through our SaaS and consulting.
You need to bring Who's on First data in to support administrative areas, it won't use admin areas from OSM. This is a bit of a technical choice (WOF has some nice features like stable IDs and a rich hierarchy, and a data format that's much easier to work with), but also the result of the Who's on First project and Pelias being developed together while we were at Mapzen.
Don't hesitate to reach out to us if you need help getting things set up.
Is there a contact point you'd prefer me to use for reaching out? I'm pretty sure I'm using WOF for bringing up Pelias but it's entirely possible I'm configuring things wrong. I'm also having a lot of trouble getting good performance out of the viewport biasing on the autocomplete endpoint (`focus.point`). Photon has `location_bias_scale` which allowed me to do very strong viewport biasing for zoomed-in queries and eliminate it almost entirely when zoomed out.
Is this something that could be added? I don't mind doing a bit of legwork if need be. This is important enough that I'm willing to throw a few weeks at implementing it.
