Korean Drumming at FOSS4G Seoul:
Posted by smathermather on October 3, 2015
Korean Drumming at FOSS4G Seoul:
Posted by smathermather on October 3, 2015
Posted by smathermather on October 3, 2015
In order to function at a most basic level in a given society (which I do not yet in the South Korean context), it is good to know the basic words of courtesy — the equivalents of “Excuse me”, “Pardon me”, “Nice to meet you”, “Hello”, “Goodbye”, etc..
Today we’ll talk about how to say “I’m sorry.” Between talking across cultural / language / expectation differences, and just spending time with individuals you might not know well, being able to apologize is a very important tool in the toolkit.
Mian (mee ahn) is the root of one way of apologizing in Korean. Often you’ll be saying this formally, so Mianheyo (미안해요) would be what you would say to apologize. If you don’t need the formal, usually you’ll say “Mianhe” 미안해.
For a more comprehensive coverage of apologies (plus pronunciation!), see Sweet and Tasty TV’s coverage of this:
Posted by smathermather on September 28, 2015
I posted this on Twitter and Facebook, but I really like how this time lapse turned out. This is shot in a single take with a single video. Maybe wordpress won’t over-compress it like the others… .
Posted by smathermather on August 31, 2015
For me, understanding a language, beyond a memorization of terms, is predicated on the idea that I understand something of the underlying logic to the language. So today, instead of a Korean word, we’ll talk about the term agglutinative. (bless you)
In short, what it means is that a language uses a lot of prefixes, stem words, and suffixes, and that these components of larger words don’t change their sound in order to be put together.
Let’s take some English words as a counter example. When we look at English numbering, we have this weird thing that happens in the teens. The first thing we notice, is that for numbers between 10 and 20, we call them teens not tens. English is not agglutinative, it is fusional. When prefixes and suffixes come into play, often (but not always) the sounds change. Think of thirteen (not three-ten or three-teen) vs. Fourteen. Fifteen is another departure — we might expect five-teen.
And don’t even get me started on twenty (two tens), or thirty (three tens)… .
By contrast, Sino-Korean numerals are agglutinative.
FYI, in the Korean Language, there are two numbering systems: the native Korean system, and the Sino-Korean system. More on that another time.
So, if I say the number three (sam), the number ten (sheep), and the number three again (still sam), I get 33, or sam sheep sam: 삼십삼. If I want to say 13, that’s just sheep sam, or 십삼. You prefer the number 88? Well that’s 팔십팔, or pal sheep pal.
FYI, the proper romanization of the word 10 (십) is “sip”, but as the s sound in front of the long e sound is pronounced sh, we’ll just consider the whole process an homage to counting sheep. Somehow apropos given the nation is 13 time zones away from me… .
Posted by smathermather on August 30, 2015
A good logo is hard to come by. I love the logo of Korean National Park Service. It’s simple, beautiful, has elements of complexity to it, and makes a simple statement: land of mountains and sea. The mountains and the sea are sources of life in Korea, from the resources and farming found on the edge of the mountains, the peace found hiking and visiting temples in the mountains, to the resources and seafood found in the sea. More to the point with KNPS, many of the national parks lands are reserves of mountains or protected ocean.
Today we will look at the second word in our mini-series on Korean words (see the first here): the Korean word for mountain: san.
Look to the individual characters that make up the syllable, and we see ㅅ(s),ㅏ(ah),ㄴ(n). This is a simple enough word.
As Seoul is surrounded by mountains, you will encounter san as a syllable in many contexts. Take for example a mountain to the north of Seoul, Bukhan Mountain, or Bukhansan: 북한산. This name mirrors one of the names of North Korea: Bukhan. Buk means north, Han is the river that flows through Seoul. So the full name is “Mountain north of the Han”.
Buhkansan 북한산 is also the name of the national park that contains the mountain it is named for.
If you visit Seoul for FOSS4G, I highly recommend a hike in the mountains. It’s a rare megacity and capital that contains a 30 square mile national park inside its boundary. If you do visit, I recommend doing so during the week — weekend visits are very busy.
Posted by smathermather on August 29, 2015
That could be my whole blog post. Just a PSA. Google Maps in Seoul is like Apple Maps was when they launched — dangerously inaccurate. *I don’t know what is helpful on iOS. I traveled last year with Android only, and my searches so far on iOS are coming up short.*
So what should you use? Anything OSM-based isn’t too bad. I really like OSMAnd. I haven’t done any deep analyses in this space, but OSMAnd has served me well. Also, you can record tracks, so if you see something wrong or out of date, OSMAnd will help you fix it in OpenStreetMap.
I adore Seoul’s subway system. It’s considered one of the largest in the world, ranks among the best, cleanest, etc.. Many stations are like 5 story malls that happen to have trains at the bottom; it’s really surreal. Oh, and for an English speaker it is not hard at all to navigate. Almost everything is in romanized characters / English + Korean, and the trains play nice sounding music as they approach.
It doesn’t hurt to have a good app, however. Subway Korea, though a little strange in interface is absolutely amazing once you use it. I say the interface is weird — it’s just transit graphic at a single static scale (it doesn’t change appearance as you zoom). But that graphic allows you to route between locations calculating train changes as necessary, let’s you optimize for time vs. number of train changes, and allows you to do routes by way of particular stops you may want to take on the way. It is great in large part because it’s designed with a deep understanding of how transit works and the kinds of questions people who don’t know the system need answers to. That’s a tall task. I can recall my first time navigating public transit in Boston, Cleveland, New York, DC, San Francisco, Portland, and Denver. Each of the above (even Portland!) was a little more difficult than Subway Korea and Seoul’s amazing wayfinding.
Posted by smathermather on July 13, 2015
Dirk’s MSF Canada Drone Day is officially the first blog post I have “re-blogged”. Please read: https://smathermather.wordpress.com/2015/07/13/msf-canada-drone-day/
or better yet here: http://dirkgorissen.com/2015/07/14/msf-canada-drone-day/
I had the pleasure of co-presenting with Dirk and Ivan, and the rest is well covered in Dirk’s post. It came together as an excellent day and I think you would be hard pressed to have had a better introduction to drones.
The day was valuable to me as an emerging practitioner. I learned more about the state of the art in hardware, software, regulations, philosophy, and RC control from this day, and it was inspiring to inhabit the same space with such dedicated practitioners for a short time.
Beyond the value of the workshop to the participants, the outcomes were the following, this quoted from Dirk’s post:
As a first milestone we are looking to pull together a proposal to the Humanitarian Innovation Fund in collaboration with OpenDroneMap and supported by the Missing Maps consortium.
I love the extension of ODM into this space. This is the real value of open source, the opportunity to collaborate across the world, across industries and use cases, and across organizations. Expect to see improvements to ODM in usability, performance, and output qualities from this initiative. More on this later.
Another outcome / learning for me was observing Ivan’s OpenUAV. From his repo:
This is intended to be a repository for design files, instructions, photos, documentation, and everything else needed for people wishing to build a and operate UAV (drone) in a low-income, resource-poor environment. This is not about cutting-edge UAVs, it’s about democratizing the technology and getting it into the hands of more people, particularly in poorer countries and humanitarian settings.
Ivan undersells it. This is a pro quality quad copter on a very nice price diet — a brilliant piece of pragmatic engineering.
This little quad copter will make its way into drone building workshops I’ll be offering in Cleveland and Columbus Ohio and Seoul, South Korea in August and September. More details forthcoming.
If you are in Cleveland, plan to be at FOSS4G Seoul, or Ohio GIS, come build Ivan’s capable quad.
(BTW, Ivan says with a couple of 4C 8000mAh batteries, this sucker flies for 50 minutes… .)
Posted in 3D, Bundler, Camera Calibration, FOSS4G, Image Processing, OpenDroneMap, OpenDroneMap, Optics, Photogrammetry, PMVS | Tagged: 3D, bundler, Doctors without Borders, drones, FOSS, MSF, ODM, opendronemap, sUAS, UAV | Leave a Comment »
Posted by smathermather on June 7, 2015
Citing my previous post, let’s move on to more specifics on my thoughts regarding the integration of OpenAerialMap, OpenDroneMap, and MapKnitter as projects.
OpenAerialMap will become a platform by which drone users can share their imagery under an open license.
So, as the metadata spec for OpenAerialMap and OpenImageryNetwork matures, and as soon as a publicly available place for drone users to push their data comes online, ODM will write appropriate metadata and geotiffs to go into OIN to be indexed by OAM. Probably as an added bonus, ODM should be able to optionally auto-upload outputs from to the appropriate node on the OpenImageryNetwork.
MapKnitter / ODM integration is pretty straight forward in my mind too. There are ways that MapKnitter complements ODM, and vice versa. ODM does not have a graphical user interface at this time. MapKnitter promises to fill that role in a future OpenDroneMap implementation. MapKnitter has no image blending or auto-matching tools. OpenDroneMap will soon have both.
These projects (plus OpenTerrain…) are really exciting in their own right. Together, they represent amazing opportunities to foster, cultivate, process, and serve a large community of imagery providers, from individuals and small entities capturing specific datasets using kites, drones, and balloons, to satellite imagery providers hosting their own “image buckets” of open imagery data. Exciting times.
Posted in 3D, Bundler, Camera Calibration, FOSS4G, Image Processing, OpenDroneMap, Optics, Photogrammetry, PMVS | Tagged: 3D, bundler, drones, FOSS, MapKnitter, ODM, Open Terrain, OpenAerialMap, opendronemap, sUAS, UAV | Leave a Comment »
Posted by smathermather on May 29, 2015
is the beginning of some fruitful discussion, I suspect. There are some really awesome projects gaining momentum. I’ll give an overview of them as best I am able.
Let’s start with the one nearest and dearest to my heart (if you’ve been reading my blog, you can skip this part): OpenDroneMap. OpenDroneMap is an open source toolkit for processing drone, balloon, kite imagery into geographic data. It does this by using fully automated feature-matching between images, which create a 3D point cloud. From that, we can create a 3D surface (mesh), textured mesh, and orthophoto. This guy says it better:
But, it’s just a stand alone, Linux (Ubuntu)-based tool. It requires some geekiness to run, and it does not (at least not yet) act as a platform. By that I mean, generically, you can’t just upload images to it and get the wonderful output from a service, and we don’t have a place to store and share all this wonderful data that comes from and will be coming from drones and other aerial platforms. This is where (from my selfish perspective) the other projects are so well timed… .
Let’s start with OpenAerialMap. From the Development Seed blog post on it (yes, you should follow the link. Don’t worry, I’ll wait until you return):
OpenAerialMap is a set of tools for searching, sharing, and using open satellite and drone imagery. This initial release includes the core infrastructure to catalog petabytes of open imagery. It also includes an extremely usable API and an elegant web interface to submit, search and download available imagery.
This is a reboot of a couple of previous attempts at solving this problem space, and it’s really exciting to watch passionate and brilliant work take place to make this happen. Also, this is not an easy problem space, and is being really thoughtfully simplified and implemented.
(As a side note, I’m not going to get into the distinction between OpenAerialMap and OpenImageryNetwork — not today anyway)
Open Terrain is a project for which a portion of its scope is to do for terrain models what OpenAerialMap and OpenImageryNetwork will do for open aerial datasets. The projects are informing each other and growing together, which is awesome collaboration to observe.
Finally, Mapknitter has recently been rebooted too, and it’s now a really elegant tool for taking a few aerial images and knitting them into a usable map (ok, it always was p. cool — now it’s even more elegant). What’s great about MapKnitter is it specifically addresses the problem of georeferencing balloon, kite, or drone images in a simple-to-use interface in the browser.
So, back to the question:
Bravo, yes. Lets. I have been thinking about, talking to people, discerning the strengths, overlaps, and complementary fittings of these projects as they have emerged. We are headed toward some really great things… . More specific thoughts to come.
Posted in 3D, Bundler, Camera Calibration, FOSS4G, Image Processing, OpenDroneMap, Optics, Photogrammetry, PMVS | Tagged: 3D, bundler, drones, FOSS, MapKnitter, ODM, Open Terrain, OpenAerialMap, opendronemap, sUAS, UAV | 1 Comment »