lpetting

this is cool; i like that you used it continuously while building it/ built it for your own needs. are there any kinds of searches it does particularly well at? any fun hot takes come up in your summarizers?

i am not surprised that 'the way you clean and process the data substantially changes the quality of the results.' can you share anything about your approach here?

love what you all are doing, and wish i had this when i worked at airbnb. the reactivity update is killer!

I'm glad.

The frustrations you mention are some of the primary reasons we started iggy. There's a lot to this so I'll respond to your concerns one by one.

- You can store our data for thirty days, and that can be extended to month-to-month as long as you have a subscription. (This is covered in the 'SERVICE.' section of our TOS) Just keep in mind it will get stale if not updated on some cadence. - Price: we are a new startup and inevitably have a lot to learn about pricing, but we will always communicate any pricing changes (This is covered in the "FEES AND PAYMENTS." Section of our TOS) - We do require attribution, and there are many ways to do this-- happy to chat more about options here. (This is covered in the "CUSTOMER RESPONSIBILITIES." Section of our TOS). To keep in mind, OSM data does come with a license that is still in effect if you are using it via our API. (osm attribution, and share alike when combined with other data, helpful info here: https://wiki.osmfoundation.org/wiki/Licence/Licence_and_Lega...). - You can combine our data w other sources. (Why? Iggy is founded by engineers, data scientists and others who get that this is how data becomes useful.) - You can share our data on other maps unless otherwise specified (i.e. our datasets that start with 'licensed_'; see dataset-specific info in our data catalog (linked above))

Does that help? If you have any other questions about this please don't hesitate to reach out to me at [email protected]

Thanks for posting! I'm Lindsay, the CEO of Iggy.

I was a Data Scientist at Airbnb for ~5 years and was shocked at how little we knew and leveraged about location in our product and models. I had done a lot of GIS work in grad school and knew it could be better, so I left last year to start Iggy. Turns out Airbnb wasn't the only company to struggle with this-- so many other cos in travel, real estate and insurance have trouble building, maintaining and leveraging geographic and location data. We've been working with a few in stealth, and are excited to now open up our APIs for broader use.

I am happy to answer any questions folks may have. In the meantime: - check out our launch blog here: https://medium.com/iggy-tech/launching-iggy-self-serve-apis-... - API ref: https://docs.askiggy.com/reference/features-1 - follow us here: https://twitter.com/askiggyapp

For real. No reason w can't build it as a service! (I'm the CEO of Iggy)

You're right that there's a ton of OSM data that most people can't use. We want to change that and give access to so much more. Follow us on Twitter at https://mobile.twitter.com/askiggyapp for lots more code samples this week and demos to come!