<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Right – it isn’t just about the rendering, but about
the underlying data. A POI should be considered a universal point of interest –
ala a landmark of building that would be included in a ‘Guide to XXX City’.
Loading up on all the businesses is changing from being a map to a yellowpages –
which is fine if that is the idea of the project. Keeping this data upto date
is far harder than actual pathways – and once businesses are no longer
operating, the data will be bad – and that is a dangerous path to go
down.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>-A<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Eugene Alvin Villar
[mailto:seav80@gmail.com] <br>
<b>Sent:</b> Wednesday, May 06, 2009 11:58 AM<br>
<b>To:</b> Ahmed Farooq<br>
<b>Cc:</b> maning sambale; OSM<br>
<b>Subject:</b> Re: POIs Part 2<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Wed, May 6, 2009 at 11:40 PM, Ahmed Farooq <<a
href="mailto:ahmed@enthropia.com">ahmed@enthropia.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p>I have to add – have you seen the Boracay map? While it looks
fantastic that it is all mapped out, naming each resort/business there has lead
to a map that looks absolutely bloated and is unreadable at times.<o:p></o:p></p>
<p>For example <a
href="http://www.openstreetmap.org.ph/map/c/11.960549689657205/121.925368309021/17/"
target="_blank">http://www.openstreetmap.org.ph/map/c/11.960549689657205/121.925368309021/17/</a>
- “Mango Ray Shenna’s Resort” – are those two places?
One? Which building is covered by their name? Multiple buildings or just one?<o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>This is a rendering problem,
not a problem of data collection. It's theoretically possible to add more
metadata to those resorts (like N-star rating) so that a renderer can choose
to, say, display only 4- and 5-star resorts so as not to clutter a
general-purpose map. This can be tied to zoom levels so that at a low zoom level,
only Boracay Regency, Discovery Shores, Friday's, Shangri-La Boracay, etc. will
be displayed or labeled. At higher zoom levels, more detail and labels can then
be displayed.<o:p></o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p>A POI should be a notable location that a tourist may be interested in
– a statue, a building, even a public transit location. But specific
businesses (be it fast food joints or specific resorts) only create clutter and
a mess – which will only get worse as businesses are created and others
go out of business.<o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Having too much data (especially
as part of the primary data set) is contrary to the spirit of an open
user-maintained map.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=MsoNormal>Well, I generally think that some types or classes of data
are good additions to the primary data set.<br>
<br>
For instance, Asiatype publishes a paper map of the Makati CBD and Ortigas
business districts showing the locations of all the buildings. I don't think
having those buildings in OSM is "too much data". Likewise, I think
the location of all resorts in Boracay is a class of data that would be a good
addition to OSM.<br>
<br>
Detached (as in stand-alone) restaurants and other dining places are OK in my
opinion; they provide vital landmark info as Rally has said.<br>
<br>
On the other hand, I oppose the systematic addition of *all* tenants inside
shopping malls. Some are OK (like the anchor tenants that I've mentioned in a
previous e-mail).<br>
<br>
<br>
-- <br>
<a href="http://vaes9.codedgraphic.com">http://vaes9.codedgraphic.com</a><o:p></o:p></p>
</div>
</body>
</html>