[Talk-ko] Talk-ko Digest, Vol 25, Issue 2

[Brian McLaughlin]

Andrew,
It would be possible to fetch the English names, and replace the data
locally, but I want to update frequently without doing a lot of work. I
also want the slippy map to look a little cleaner since I use it as a
basemap for my project (http://www.openbaekdudaegan.org/maps.html). I  want
to use the Korean names in conjunction with the English name on other map
products both digital and print. The easiest way of doing this to alter the
name field convention (name= 이름 Name.) I think it's helpful to use hyphens
where appropriate. If you want to look at a small sample I did
http://www.openstreetmap.org/?lat=35.6505&lon=127.5562&zoom=14&layers=M. I
don't see any useful purpose for adding the parentheses around the
romanized place names. Please let me know if I am missing something.

Thanks again for your input and happy mapping.
Brian

On Mon, Jan 21, 2013 at 9:00 PM, <talk-ko-request at openstreetmap.org> wrote:

> Send Talk-ko mailing list submissions to
>         talk-ko at openstreetmap.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.openstreetmap.org/listinfo/talk-ko
> or, via email, send a message with subject or body 'help' to
>         talk-ko-request at openstreetmap.org
>
> You can reach the person managing the list at
>         talk-ko-owner at openstreetmap.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Talk-ko digest..."
>
> Today's Topics:
>
>    1. Re: Talk-ko Digest, Vol 25, Issue 1 (Brian McLaughlin)
>    2. Re: Talk-ko Digest, Vol 25, Issue 1 (Andrew Errington)
>
>
> ---------- Forwarded message ----------
> From: Brian McLaughlin <brian.scott.mclaughlin at gmail.com>
> To: talk-ko at openstreetmap.org
> Cc:
> Date: Sun, 20 Jan 2013 21:36:45 +0900
> Subject: Re: [Talk-ko] Talk-ko Digest, Vol 25, Issue 1
>
> Robert,
>
> Thanks for your quick reply and useful insight. Good Idea to use an extra
> space between the Hangeul and Roman characters to give the text a little
> extra buffer. I did mean to leave a space, but maybe two spaces are better. As
> far as the suffix translations go, I was just throwing that out there. I
> could care less about that. I would be happy to leave the name:en as is. I
> don’t want to make things more complicated than they have to be. That tag
> isn’t even rendered anyway.
>
> I’m most concerned with the generic name tag, since it makes the labels
> really hard to read on my GPS and hand phone, and if puts unnecessary
> characters on my paper maps. Plus I think it makes the slippy map a little
> cluttered too. Hopefully I can get some more feedback from others. I don’t
> want to rock the boat and start changing accepted conventions with just
> cause and peer support.
>
> Safe and Happy Mapping to you too,
> Brian
>
>
>
> Andrew ,
>
> Thanks for your quick reply and support.
>
> Thanks for your support. I checked out the link and when they get it
> working that will be great. But it’s not really feasible for me to
> implement. It would take a very powerful server with lots of bandwidth and
> disk space to make that work with my project. However, as long as we tag
> our features correctly, I’m sure whatever we do will compatible with their
> project. I personally think it’s useful to have both the Hangeul and roman
> names rendered together.
>
> As far as the Multilingual Map Project, I have a good idea how they did
> it. I’m guessing that first they rendered their own tiles without labels,
> and then they are overlaying them with vector labels from a separate
> database. Currently when you look at OSM and other web maps such as Google
> and Naver, what you are seeing is a collection of georeferenced  .png
> images. The technology works great, but you can’t change the variables once
> they’re rendered. In a few years I’m sure the technology will be available
> to effectively deliver the same data in vector format allowing users to
> customize the rendered images to their own liking. But that’s going to
> require some pretty powerful servers and lots of bandwidth to work.
>
> Brian
>
>
>
>
> ---------- Forwarded message ----------
> From: Andrew Errington <erringtona at gmail.com>
> To: talk-ko at openstreetmap.org
> Cc:
> Date: Mon, 21 Jan 2013 20:31:33 +0900
> Subject: Re: [Talk-ko] Talk-ko Digest, Vol 25, Issue 1
> Hi Brian,
>
> Is there some way that you can process the data before you use it?  For
> example, if you want 'English' fetch all the name tags for everything in
> the
> area you are interested in and then overwrite name=* with the contents of
> name:en (if present), then pass the data on to the GPS (or phone, or map
> drawing program).
>
> Best wishes,
>
> Andrew
>
>
> On Sun, 20 Jan 2013 21:36:45 Brian McLaughlin wrote:
> > Robert,
> >
> > Thanks for your quick reply and useful insight. Good Idea to use an extra
> > space between the Hangeul and Roman characters to give the text a little
> > extra buffer. I did mean to leave a space, but maybe two spaces are
> better.
> > As far as the suffix translations go, I was just throwing that out
> there. I
> > could care less about that. I would be happy to leave the name:en as is.
> I
> > don’t want to make things more complicated than they have to be. That tag
> > isn’t even rendered anyway.
> >
> > I’m most concerned with the generic name tag, since it makes the labels
> > really hard to read on my GPS and hand phone, and if puts unnecessary
> > characters on my paper maps. Plus I think it makes the slippy map a
> little
> > cluttered too. Hopefully I can get some more feedback from others. I
> don’t
> > want to rock the boat and start changing accepted conventions with just
> > cause and peer support.
> >
> > Safe and Happy Mapping to you too,
> > Brian
> >
> >
> >
> > Andrew ,
> >
> > Thanks for your quick reply and support.
> >
> > Thanks for your support. I checked out the link and when they get it
> > working that will be great. But it’s not really feasible for me to
> > implement. It would take a very powerful server with lots of bandwidth
> and
> > disk space to make that work with my project. However, as long as we tag
> > our features correctly, I’m sure whatever we do will compatible with
> their
> > project. I personally think it’s useful to have both the Hangeul and
> roman
> > names rendered together.
> >
> > As far as the Multilingual Map Project, I have a good idea how they did
> it.
> > I’m guessing that first they rendered their own tiles without labels, and
> > then they are overlaying them with vector labels from a separate
> database.
> > Currently when you look at OSM and other web maps such as Google and
> Naver,
> > what you are seeing is a collection of georeferenced  .png images. The
> > technology works great, but you can’t change the variables once they’re
> > rendered. In a few years I’m sure the technology will be available to
> > effectively deliver the same data in vector format allowing users to
> > customize the rendered images to their own liking. But that’s going to
> > require some pretty powerful servers and lots of bandwidth to work.
> >
> > Brian
>
>
>
>
>
> _______________________________________________
> Talk-ko mailing list
> Talk-ko at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-ko
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ko/attachments/20130121/27bdb75b/attachment.html>