Search by location
21 views
Skip to first unread message
wosd
Feb 18, 2011, 4:31:06 AM2/18/11
to Plancast API
Hi guys,
any chance to get a list of plans for custom location search?
Something like:
http://api.plancast.com/02/plans/where.json?where=Boston&count=15
returns 1-50 plans for Boston.
any chance to get a list of plans for custom location search?
Something like:
http://api.plancast.com/02/plans/where.json?where=Boston&count=15
returns 1-50 plans for Boston.
Mark Hendrickson
Feb 19, 2011, 4:13:31 PM2/19/11
to planca...@googlegroups.com, wosd
Yep, this is something we should have ready next week. I'll ping the list when it's available, along with an endpoint for pulling plans by category.
Mark
--
Mark Hendrickson
My plans: http://plancast.com/mark
My info: http://ursusrex.com | http://about.me/mark
My tweets: http://twitter.com/mhendric
Mark Hendrickson
My plans: http://plancast.com/mark
My info: http://ursusrex.com | http://about.me/mark
My tweets: http://twitter.com/mhendric
Mike Dierken
Mar 5, 2011, 7:23:20 PM3/5/11
to Plancast API
Is it next week yet?
On Feb 19, 1:13 pm, Mark Hendrickson <m...@plancast.com> wrote:
> Yep, this is something we should have ready next week. I'll ping the list
> when it's available, along with an endpoint for pulling plans by category.
>
> Mark
>
On Feb 19, 1:13 pm, Mark Hendrickson <m...@plancast.com> wrote:
> Yep, this is something we should have ready next week. I'll ping the list
> when it's available, along with an endpoint for pulling plans by category.
>
> Mark
>
Mark Hendrickson
Mar 5, 2011, 8:01:48 PM3/5/11
to planca...@googlegroups.com, Mike Dierken
Sorry for the delay on this, got pushed back by other things. Good news is that I have time tomorrow to get it place for you guys. Thanks for the nudge!
Mark
Mike Dierken
Mar 6, 2011, 12:41:18 PM3/6/11
to Mark Hendrickson, planca...@googlegroups.com
That sounds great.
My app currently only has lat/long - will that be supported?
If so, what would the URL format look like? (I can probably toss that
in this afternoon if I know the syntax)
My app currently only has lat/long - will that be supported?
If so, what would the URL format look like? (I can probably toss that
in this afternoon if I know the syntax)
Mike
Mark Hendrickson
Mar 6, 2011, 2:55:42 PM3/6/11
to planca...@googlegroups.com, Mike Dierken
Yep I'll set it up to take a lat/long.
Not 100% sure what the URL format will be like. Will get back to you about that once I sort it out more.
Mark
Mike Dierken
Mar 6, 2011, 3:41:17 PM3/6/11
to Mark Hendrickson, planca...@googlegroups.com
Cool!
I'm deploying an update now, but without lat/long - just to see how
the formatting, etc. all work out.
http://geonote.org/plans
I'm deploying an update now, but without lat/long - just to see how
the formatting, etc. all work out.
http://geonote.org/plans
Here are some sample URL query terms from other services
flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
Mike
Mark Hendrickson
Mar 6, 2011, 11:18:30 PM3/6/11
to planca...@googlegroups.com, Mike Dierken
The new endpoint for querying by location is ready. I hope to have real documentation up for it before too long, but we'll need to migrate off Google Groups since they no longer let us edit or add pages. And that'll have to wait until at least after SXSW.
To get all plans in a given area, use this:
The scope needs to be set as "local" (vs. "everywhere", or null -- same thing). And pass both a "lat" and "lon".
If you want to get only plans that fall within a given category, modify it as such:
Notice the "category" param which is the name of the category. And the "type" param which specifies we want plans that match a category.
Both of these default to 50 miles of radius. If anybody wants this to be flexible, let me know and I can add a param for it.
Mark
noinput
Mar 7, 2011, 12:19:31 AM3/7/11
to Plancast API
fantastic, would love to see the mile radius added. thanks for getting
this in the system.
j.
On Mar 6, 8:18 pm, Mark Hendrickson <m...@plancast.com> wrote:
> The new endpoint for querying by location is ready. I hope to have real
> documentation up for it before too long, but we'll need to migrate off
> Google Groups since they no longer let us edit or add pages. And that'll
> have to wait until at least after SXSW.
>
> To get all plans in a given area, use this:
>
> http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&-12...
this in the system.
j.
On Mar 6, 8:18 pm, Mark Hendrickson <m...@plancast.com> wrote:
> The new endpoint for querying by location is ready. I hope to have real
> documentation up for it before too long, but we'll need to migrate off
> Google Groups since they no longer let us edit or add pages. And that'll
> have to wait until at least after SXSW.
>
> To get all plans in a given area, use this:
>
>
> The scope needs to be set as "local" (vs. "everywhere", or null -- same
> thing). And pass both a "lat" and "lon".
>
> If you want to get only plans that fall within a given category, modify it
> as such:
>
> http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&-12...
> The scope needs to be set as "local" (vs. "everywhere", or null -- same
> thing). And pass both a "lat" and "lon".
>
> If you want to get only plans that fall within a given category, modify it
> as such:
>
>
> Notice the "category" param which is the name of the category. And the
> "type" param which specifies we want plans that match a category.
>
> Both of these default to 50 miles of radius. If anybody wants this to be
> flexible, let me know and I can add a param for it.
>
> Mark
>
>
>
>
>
> On Sun, Mar 6, 2011 at 12:41 PM, Mike Dierken <dier...@gmail.com> wrote:
> > Cool!
> > I'm deploying an update now, but without lat/long - just to see how
> > the formatting, etc. all work out.
> > http://geonote.org/plans
>
> > Here are some sample URL query terms from other services
> > flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
> > geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
>
> > Mike
>
> > On Sun, Mar 6, 2011 at 11:55 AM, Mark Hendrickson <m...@plancast.com>
> Notice the "category" param which is the name of the category. And the
> "type" param which specifies we want plans that match a category.
>
> Both of these default to 50 miles of radius. If anybody wants this to be
> flexible, let me know and I can add a param for it.
>
> Mark
>
>
>
>
>
> On Sun, Mar 6, 2011 at 12:41 PM, Mike Dierken <dier...@gmail.com> wrote:
> > Cool!
> > I'm deploying an update now, but without lat/long - just to see how
> > the formatting, etc. all work out.
> > http://geonote.org/plans
>
> > Here are some sample URL query terms from other services
> > flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
> > geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
>
> > Mike
>
> > wrote:
> > > Yep I'll set it up to take a lat/long.
> > > Not 100% sure what the URL format will be like. Will get back to you
> > about
> > > that once I sort it out more.
> > > Mark
>
> > > Yep I'll set it up to take a lat/long.
> > > Not 100% sure what the URL format will be like. Will get back to you
> > about
> > > that once I sort it out more.
> > > Mark
>
> > > On Sun, Mar 6, 2011 at 9:41 AM, Mike Dierken <dier...@gmail.com> wrote:
>
> > >> That sounds great.
> > >> My app currently only has lat/long - will that be supported?
> > >> If so, what would the URL format look like? (I can probably toss that
> > >> in this afternoon if I know the syntax)
>
> > >> Mike
>
> > >> On Sat, Mar 5, 2011 at 5:01 PM, Mark Hendrickson <m...@plancast.com>
>
> > >> That sounds great.
> > >> My app currently only has lat/long - will that be supported?
> > >> If so, what would the URL format look like? (I can probably toss that
> > >> in this afternoon if I know the syntax)
>
> > >> Mike
>
> > >> wrote:
> > >> > Sorry for the delay on this, got pushed back by other things. Good
> > news
> > >> > is
> > >> > that I have time tomorrow to get it place for you guys. Thanks for the
> > >> > nudge!
> > >> > Mark
>
> > >> > On Sat, Mar 5, 2011 at 4:23 PM, Mike Dierken <dier...@gmail.com>
> > >> > Sorry for the delay on this, got pushed back by other things. Good
> > news
> > >> > is
> > >> > that I have time tomorrow to get it place for you guys. Thanks for the
> > >> > nudge!
> > >> > Mark
>
Mike Dierken
Mar 7, 2011, 1:55:28 AM3/7/11
to Mark Hendrickson, planca...@googlegroups.com
Great! Thank you for this new service.
I've deployed an updated to my app - http://geonote.org/plans
I've deployed an updated to my app - http://geonote.org/plans
Mike
Gatheringpoint
Apr 11, 2011, 5:43:16 PM4/11/11
to Plancast API
Consider this a second vote for radius support for lat/lon searches -
better yet, a google maps style bounding box.
Spencer
On Mar 6, 9:18 pm, Mark Hendrickson <m...@plancast.com> wrote:
> The new endpoint for querying by location is ready. I hope to have real
> documentation up for it before too long, but we'll need to migrate off
> Google Groups since they no longer let us edit or add pages. And that'll
> have to wait until at least after SXSW.
>
> To get all plans in a given area, use this:
>
> http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&-12...
better yet, a google maps style bounding box.
Spencer
On Mar 6, 9:18 pm, Mark Hendrickson <m...@plancast.com> wrote:
> The new endpoint for querying by location is ready. I hope to have real
> documentation up for it before too long, but we'll need to migrate off
> Google Groups since they no longer let us edit or add pages. And that'll
> have to wait until at least after SXSW.
>
> To get all plans in a given area, use this:
>
>
> The scope needs to be set as "local" (vs. "everywhere", or null -- same
> thing). And pass both a "lat" and "lon".
>
> If you want to get only plans that fall within a given category, modify it
> as such:
>
> http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&-12...
> The scope needs to be set as "local" (vs. "everywhere", or null -- same
> thing). And pass both a "lat" and "lon".
>
> If you want to get only plans that fall within a given category, modify it
> as such:
>
>
> Notice the "category" param which is the name of the category. And the
> "type" param which specifies we want plans that match a category.
>
> Both of these default to 50 miles of radius. If anybody wants this to be
> flexible, let me know and I can add a param for it.
>
> Mark
>
>
>
>
>
>
>
>
>
> On Sun, Mar 6, 2011 at 12:41 PM, Mike Dierken <dier...@gmail.com> wrote:
> > Cool!
> > I'm deploying an update now, but without lat/long - just to see how
> > the formatting, etc. all work out.
> > http://geonote.org/plans
>
> > Here are some sample URL query terms from other services
> > flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
> > geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
>
> > Mike
>
> > On Sun, Mar 6, 2011 at 11:55 AM, Mark Hendrickson <m...@plancast.com>
> Notice the "category" param which is the name of the category. And the
> "type" param which specifies we want plans that match a category.
>
> Both of these default to 50 miles of radius. If anybody wants this to be
> flexible, let me know and I can add a param for it.
>
> Mark
>
>
>
>
>
>
>
>
>
> On Sun, Mar 6, 2011 at 12:41 PM, Mike Dierken <dier...@gmail.com> wrote:
> > Cool!
> > I'm deploying an update now, but without lat/long - just to see how
> > the formatting, etc. all work out.
> > http://geonote.org/plans
>
> > Here are some sample URL query terms from other services
> > flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
> > geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
>
> > Mike
>
> > wrote:
> > > Yep I'll set it up to take a lat/long.
> > > Not 100% sure what the URL format will be like. Will get back to you
> > about
> > > that once I sort it out more.
> > > Mark
>
> > > Yep I'll set it up to take a lat/long.
> > > Not 100% sure what the URL format will be like. Will get back to you
> > about
> > > that once I sort it out more.
> > > Mark
>
> > > On Sun, Mar 6, 2011 at 9:41 AM, Mike Dierken <dier...@gmail.com> wrote:
>
> > >> That sounds great.
> > >> My app currently only has lat/long - will that be supported?
> > >> If so, what would the URL format look like? (I can probably toss that
> > >> in this afternoon if I know the syntax)
>
> > >> Mike
>
> > >> On Sat, Mar 5, 2011 at 5:01 PM, Mark Hendrickson <m...@plancast.com>
>
> > >> That sounds great.
> > >> My app currently only has lat/long - will that be supported?
> > >> If so, what would the URL format look like? (I can probably toss that
> > >> in this afternoon if I know the syntax)
>
> > >> Mike
>
> > >> wrote:
> > >> > Sorry for the delay on this, got pushed back by other things. Good
> > news
> > >> > is
> > >> > that I have time tomorrow to get it place for you guys. Thanks for the
> > >> > nudge!
> > >> > Mark
>
> > >> > On Sat, Mar 5, 2011 at 4:23 PM, Mike Dierken <dier...@gmail.com>
> > >> > Sorry for the delay on this, got pushed back by other things. Good
> > news
> > >> > is
> > >> > that I have time tomorrow to get it place for you guys. Thanks for the
> > >> > nudge!
> > >> > Mark
>
Mike Dierken
Apr 11, 2011, 6:49:18 PM4/11/11
to planca...@googlegroups.com, Gatheringpoint
I'd forgotten about the radius - my app is working well without it but
I definitely would use it.
I definitely would use it.
It would also be helpful to have the response contain the lat/long of
the events returned. This allows my mobile web app to enable browsing
by 'nearby' plans and events.
Here is an example of the data pulled from Plancast (it looks very nice)
http://geonote.org/places/plans/?lat=47.681487&long=-122.208735
Here is an example from Hunch, with the 'nearby' links.
http://geonote.org/places/hunches/?lat=47.681487&long=-122.208735
Mike
Mark Hendrickson
Apr 11, 2011, 7:06:47 PM4/11/11
to Plancast API
As an FYI, it appears there was a typo in my URL for the geo scoping,
in that it was missing the "lon" variable. May be self-evident but
here's a correct version in case anyone is confused:
http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&lon=-122.26
Mark
On Mar 6, 9:18 pm, Mark Hendrickson <m...@plancast.com> wrote:
> The new endpoint for querying by location is ready. I hope to have real
> documentation up for it before too long, but we'll need to migrate off
> Google Groups since they no longer let us edit or add pages. And that'll
> have to wait until at least after SXSW.
>
> To get all plans in a given area, use this:
>
> http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&-12...
in that it was missing the "lon" variable. May be self-evident but
here's a correct version in case anyone is confused:
http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&lon=-122.26
Mark
On Mar 6, 9:18 pm, Mark Hendrickson <m...@plancast.com> wrote:
> The new endpoint for querying by location is ready. I hope to have real
> documentation up for it before too long, but we'll need to migrate off
> Google Groups since they no longer let us edit or add pages. And that'll
> have to wait until at least after SXSW.
>
> To get all plans in a given area, use this:
>
>
> The scope needs to be set as "local" (vs. "everywhere", or null -- same
> thing). And pass both a "lat" and "lon".
>
> If you want to get only plans that fall within a given category, modify it
> as such:
>
> http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&-12...
> The scope needs to be set as "local" (vs. "everywhere", or null -- same
> thing). And pass both a "lat" and "lon".
>
> If you want to get only plans that fall within a given category, modify it
> as such:
>
>
> Notice the "category" param which is the name of the category. And the
> "type" param which specifies we want plans that match a category.
>
> Both of these default to 50 miles of radius. If anybody wants this to be
> flexible, let me know and I can add a param for it.
>
> Mark
>
>
>
>
>
>
>
>
>
> On Sun, Mar 6, 2011 at 12:41 PM, Mike Dierken <dier...@gmail.com> wrote:
> > Cool!
> > I'm deploying an update now, but without lat/long - just to see how
> > the formatting, etc. all work out.
> > http://geonote.org/plans
>
> > Here are some sample URL query terms from other services
> > flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
> > geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
>
> > Mike
>
> > On Sun, Mar 6, 2011 at 11:55 AM, Mark Hendrickson <m...@plancast.com>
> Notice the "category" param which is the name of the category. And the
> "type" param which specifies we want plans that match a category.
>
> Both of these default to 50 miles of radius. If anybody wants this to be
> flexible, let me know and I can add a param for it.
>
> Mark
>
>
>
>
>
>
>
>
>
> On Sun, Mar 6, 2011 at 12:41 PM, Mike Dierken <dier...@gmail.com> wrote:
> > Cool!
> > I'm deploying an update now, but without lat/long - just to see how
> > the formatting, etc. all work out.
> > http://geonote.org/plans
>
> > Here are some sample URL query terms from other services
> > flickr : lat=nnn.nn&lon=nnn.nn&radius=nn
> > geonames : lat=nnn.nn&lng=nnn.nn&radius=nn
>
> > Mike
>
> > wrote:
> > > Yep I'll set it up to take a lat/long.
> > > Not 100% sure what the URL format will be like. Will get back to you
> > about
> > > that once I sort it out more.
> > > Mark
>
> > > Yep I'll set it up to take a lat/long.
> > > Not 100% sure what the URL format will be like. Will get back to you
> > about
> > > that once I sort it out more.
> > > Mark
>
> > > On Sun, Mar 6, 2011 at 9:41 AM, Mike Dierken <dier...@gmail.com> wrote:
>
> > >> That sounds great.
> > >> My app currently only has lat/long - will that be supported?
> > >> If so, what would the URL format look like? (I can probably toss that
> > >> in this afternoon if I know the syntax)
>
> > >> Mike
>
> > >> On Sat, Mar 5, 2011 at 5:01 PM, Mark Hendrickson <m...@plancast.com>
>
> > >> That sounds great.
> > >> My app currently only has lat/long - will that be supported?
> > >> If so, what would the URL format look like? (I can probably toss that
> > >> in this afternoon if I know the syntax)
>
> > >> Mike
>
> > >> wrote:
> > >> > Sorry for the delay on this, got pushed back by other things. Good
> > news
> > >> > is
> > >> > that I have time tomorrow to get it place for you guys. Thanks for the
> > >> > nudge!
> > >> > Mark
>
> > >> > On Sat, Mar 5, 2011 at 4:23 PM, Mike Dierken <dier...@gmail.com>
> > >> > Sorry for the delay on this, got pushed back by other things. Good
> > news
> > >> > is
> > >> > that I have time tomorrow to get it place for you guys. Thanks for the
> > >> > nudge!
> > >> > Mark
>
Mark Hendrickson
Apr 11, 2011, 7:08:55 PM4/11/11
to Plancast API
Add the "extensions=place" param and it'll return place data with each
event, including the latlon:
Eg http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&lon=-122.26&extensions=place
Mark
On Apr 11, 3:49 pm, Mike Dierken <dier...@gmail.com> wrote:
> I'd forgotten about the radius - my app is working well without it but
> I definitely would use it.
>
> It would also be helpful to have the response contain the lat/long of
> the events returned. This allows my mobile web app to enable browsing
> by 'nearby' plans and events.
>
> Here is an example of the data pulled from Plancast (it looks very nice)http://geonote.org/places/plans/?lat=47.681487&long=-122.208735
>
> Here is an example from Hunch, with the 'nearby' links.http://geonote.org/places/hunches/?lat=47.681487&long=-122.208735
event, including the latlon:
Eg http://api.plancast.com/02/plans/query.json?scope=local&lat=37.47&lon=-122.26&extensions=place
Mark
On Apr 11, 3:49 pm, Mike Dierken <dier...@gmail.com> wrote:
> I'd forgotten about the radius - my app is working well without it but
> I definitely would use it.
>
> It would also be helpful to have the response contain the lat/long of
> the events returned. This allows my mobile web app to enable browsing
> by 'nearby' plans and events.
>
>
> Here is an example from Hunch, with the 'nearby' links.http://geonote.org/places/hunches/?lat=47.681487&long=-122.208735
Mike Dierken
Apr 11, 2011, 9:20:17 PM4/11/11
to planca...@googlegroups.com, Mark Hendrickson
Great!
Reply all
Reply to author
Forward
0 new messages