Subscribe
Sign in
Iggy API — Build location data into your apps, fast, try for free
Iggy gives you access to >175 geographic and location-based datasets in an easy to understand and ergonomic API. No special software, no geospatial know-how required to use this location data at scale. Just a simple API request.
43
Replies
nicholas licalzi
Awesome product! Plenty of use cases in mind for this one...
Share
Excited to see the Iggy team launch their product and make it self-serve for developers. I'm thrilled to see that access to complex location data is finally available to anyone who can make an API call. Go team! 🎉
Congrats on the launch! Excited to see what people will build with access to so much data thru the APIs.
Thanks for hunting us @widawskij! We're pumped to share Iggy w you all!
?makers How does map panning affect requests? Is there a suggested way for being more frugal with requests to handle this exploratory use case? Also, it would be awesome if you had a filter for your premium datasets so it's easier to see what that price tier entails :-)
@product_at_producthunt Hey Michael, can you tell me a little bit more about your use case? As a user pans a map is it calling the API for the data in that viewport and forgetting the data queried earlier? Our license allows for caching so that would be one way to address frugality.
Thanks for the feedback on the premium datasets!
@zack_walker mostly curiosity since I've had to deal with location data in a past life. It seemed like there was always a balance we had to strike with the UX to make exploration possible, but not drive up our costs too much. Caching is definitely one strategy. Maybe session based pricing would be a different way to tackle this?
I'm Zack, co-founder and head of product at Iggy. Our mission is to make information about the world accessible. We've taken our first steps toward this over the last few months and you can now query a wide range of geographic datasets (>175!) using the Iggy API.
From flood, fault and wildfire risk to parks, rest stops, fire stations and even voting patterns, commute trends and community demographics; we’ve built a massive database (https://data.askiggy.com/) so that your apps can harness better data.
My co-founder Lindsay and I started Iggy bc we were frustrated with the number of missed opportunities we saw around geographic data at Airbnb. Even the best teams have a hard time integrating this data; the current solutions require way too much expertise and are quite developer-unfriendly. First, you need to find a source for that data, evaluate it alongside others, transform it into a useful format, and join it with your data. All of this is uniquely hard with geographic data, mostly because that data often comes in a form that is not usable without special software! Once you can open it, you have to explore the dataset, describe it, and understand the possible ranges of values. You have to find documentation — if it even exists — that explains how the data is structured. For some datasets, you need to maintain a pipeline to deal with updates. You have to monitor it and fix things when the data source inevitably changes. All of these things take a ton of time and resources and distract developers from their core jobs.
We designed our API to take the pain out of location data. You don't need any special software, python packages, or domain-specific knowledge to get geographic data and location context into whatever you're building. We abstracted away all of the data cleaning, joins, transformations, and update pipelines so all you have to do is write a simple API query to get the data you want, and then use it however you like.
Thanks for checking us out, ask us all the questions you have, we love to chat about all things location and data.
@kevinmart_in thanks so much! would love to hear your thoughts on ways iggy could help at unspun
So excited to see what the team has accomplished. Great work and congrats @lindsay_pettingill and @zack_walker on the self-serve launch and on ProductHunt. I've been following it for a long time!
Looks very impressive! How accurate is your app? Is it possible to define if a user has entered a residential building or an office? How often do you update your databases?
@vadim_shcherbakov thanks for asking! Each of our datasets has a different update cadence depending on the underlying source of the data. Most of our points of interest are updated monthly, but things which change more rapidly (like wildfires) are updated several times a day. We do not yet have a buildings dataset with properties like `residential` vs `commercial` but love that idea! Would love to hear about how it would be useful to you.
