IMHO the issue of tagging entrances is a bit orthogonal to this issue. The issue here is, how to place the target of a search anywhere other than the centroid?
If there is a large polygon that someone is likely to find by searching, and want to route towards, IMHO the right solution is some kind of relation, linking the polygon to a node which represents "this is where you drive to". Perhaps this could be done under the existing "site" relation. Perhaps it needs something different. But in any case, a simple "entrance" tag on an un-associated node/way/area will not, imho, help much. Steve On Thu, Nov 18, 2010 at 8:41 PM, Nathan Edgars II <[email protected]> wrote: > Features such as parks may cover a large area, and if the park is > drawn as a polygon, routing software will likely choose the centroid. > The nearest point on public roads to the centroid may however not be > the actual entrance to the park. For example, go to > http://www.yournavigation.org/ and get directions from Orlando, FL to > Wekiwa Springs State Park (the actual entrance is in the southeast > corner; use Wisteria St, Orange County, FL). How can we make sure that > the software will know where the entrance is? > > This also applies to large resort hotels, where we would want to mark > the check-in building, and to pretty much everything large that has a > single main entrance. > > _______________________________________________ > Tagging mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/tagging > _______________________________________________ Tagging mailing list [email protected] http://lists.openstreetmap.org/listinfo/tagging
