[OSM-talk] near by

[Ramiro Cosentino]

2012/4/27 Richard Weait <richard at weait.com>

> Two things come to mind for me.
>
> First, the distance calculation does not require OSM.  If you
> generalize 20 blocks or whatever as n-meters you can calculate
> crow-flies distance with only the lat-lons.  Of course, if your want
> to route over roads (pedestrian paths) and calculate that distance,
> having the OSM data is really helpful.
>

Thanks for your input, Richard!

To be honest this is the first time I dive into implementing the "near by"
feature.
Does it have any other name apart from "near by" ? I couldn't find much
related to OSM
in this topic, but maybe because my search was a bit narrow.

I'm not sure if I'll implement pedestrian paths, it depends on how
complex/possible it is
to do it on a mobile device. For the moment I just have the tiles for the
area I need
(Buenos Aires Capital) and draw some markers using vectors from the
OpenLayers mobile lib.

Are there other ways other than generalizing on n-meters around the point
where the user is?
What are crow files?

Sorry for my ignorance, if you can point me to some docs on this topic I
will avoid doing basic questions :)

Second, if the phone has a list of POIs, I wonder if some of them
> should also be in the OpenStreetMap data base?  Are these
> generally-interesting POIs or POIs that should not be included in OSM?
>

The POIs are loaded by us. Not sure if these are called POIs as well, as
I'm guessing a POI
is a somewhat well-known and pre-defined location on the map.
In our case, the 'POIs' are determined by us, and very likely they are not
part of OSM,
as they are mainly restaurants and hotels which have an agreement with us
to appear on the app.

To simplify (without thinking of pedestrian paths) do you think there's a
way I can show our custom POIs
near by the user's current location?

Thanks a lot!
Rama
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20120427/7cf14f34/attachment.html>