a personal website slash blog
Ever wanted to know what your local subway map would look like?
The designers at Transit Authority Figures might provide an answer. They did some great work in designing subway maps for small towns without public transportation. One interesting map detail is actually the wording: the station names are well chosen, with good local knowledge, not one of those “funny” naming schemas, and it almost makes you believe you’re viewing a real one.
The tricky part of pedestrian navigation is, that it actually involves a lot of refinement work on current base maps in order to provide a good service. Using regular digital road maps, as we know them in Google Maps for instance, is just not possible. Pedestrians need different information. Most maps currently used in navigation devices are made by and for people in cars, moving at 35km/h and faster. As pedestrian you move slower, on other paths and parts of the street, your orientation senses work differently, you notice other landmarks, signs, use short-cuts, cross streets randomly and can make u-turns whenever you want to.
Nokia Maps 3.0 has some enhancements aimed to help pedestrians. I especially found the 3D-like landmark drawings on the map and the continuous reverse geocoding very helpful. I think I already mentioned in an earlier post the very well done cartography, optimized for smaller displays.
Walking directions work in most cases well. Nokia Maps knows the park next to the subway station I often use and shows me the shortest path to it.
Seems an easy task, but Google Maps, based on TeleAtlas’ road network in that area, shows some fantasy foot paths inside the park and suggests another route circling around.
OpenStreetMap shows the real layout of all foot paths in the park and provides good walking directions (by OpenRouteService) too.
The quality of the returned walking directions depend on the strength of the GPS signal in some cases. If it’s weak, Nokia Maps doesn’t dare to send you out to take a walk on a three lane street full with speeding cars.
Imagine you step out the subway station and ask Nokia Maps for the shortest way walking to your destination. If you’re lucky and the signal is good, Nokia Maps snaps you to the right street and returns good results.
Let’s assume it’s a bad GPS day and your signal is about 10m off, happens quite frequently in urban areas. Nokia snaps you on a 3 car-lane street and suggest you start walking there. Not good.
That’s what the situation looks like on the aerial. The subway station was under construction then, but there is an exit next to the containers. Anyways, a pedestrian navigation service should never propose walking on that road.
Other services I tried in that area had some problems too. Google Maps sent you on the same road. OpenRouteService basically returned a good walking route, but didn’t know that you had to jump off a 3m wall to reach the nice foot path along the canal.
A week ago Helge and I were invited to host a Digitalks session about GeoServices. Digitalks is an interesting event series in Vienna, aimed to explain recent media and technology developments to a “normal”, not so tech-savvy audience. Meral, the woman behind Digitalks, usually tries to invite early adopters or enthusiasts who are passionate about media and technology to host a session. There’s no PowerPoint in Digitalks, only live demos and hands-on are allowed, which is good and makes the presentations very lively, although it doesn’t always work as expected.
Anyways, I felt honored to be invited and talk a little about GeoServices. Helge did a brilliant job in presenting OpenStreetMap and explaining the revolutionary aspects of the project. I tried to give an overview of the grown variety of geographic applications in the internet since the first appearance of map mashups in 2005 and showing some recent location based services on a mobile device. If I’d have had a closer look at the attendees list first, I probably would’ve had chosen a few other things to demo. The ratio expert/novice of the audience was actually more leaning towards expert, so I hope it wasn’t too obvious for most people.
Thanks again to Meral for inviting us and many thanks to Luca for taping the session on video!
PS: the next Digitalks is about Microblogging, hosted by Twitter, should be interesting!
IMHO Nokia Maps 3.0 has basically two outstanding features:
While trying Nokia Maps I usually kept thinking why I would buy Nokia Maps and not use Google Maps mobile, which is a free application. If it’s only for looking up addresses and directions, and I don’t care about the mobile data connection, I’d go for Google. Google does the same or even a better job here.
When it comes to looking up POI nearby, Nokia Maps is way ahead of Google.
The other day I was looking for a post office, because the one I knew was under construction and closed (and the staff there couldn’t tell me where the nearest post office is btw). The official Austrian mail site totally failed on a mobile browser, no chance to get a list of their offices. Google returned a couple of search results considering my location, but would have sent me way far away to a post office in another district, giving nice directions with public transport though. Nokia Maps showed me two post offices in the neighborhood and provided walking directions of course.
Post offices is of course only one category in the catalogue. The POI catalogue seems very well organized and can be explored quickly, even tough it’s pretty comprehensive. I found the catalogue better usable and more efficient on mobile devices than a Google Maps mobile search for POI.
Better usable because a search for POI in Google Maps mobile requires you to stop, type and check results. A catalogue you can explore easily while walking, by using only one thumb, just like an iPod. It requires less attention than a text search.
More efficient because a Google Maps mobile search basically returns lots of locally irrelevant results. Google is probably working on that, but in the meantime Nokia delivers better, clearer and more useful local POIs.
Additionally there is an entire guide-section in the catalogue, providing mobile tourist guides I guess. Unfortunately I didn’t try this feature.
Bottom line: people who want more out of mobile maps than just address search and directions should give Nokia Maps 3.0 a shot.
WOM World approached me and asked if I would be interested to test Nokia Maps 3.0 on a Nokia 6210 Navigator. I agreed and they sent me a test device last week. This is the first post out of a short series, I hope.
Unlike others, I received a two-pin plug in a two-pin plug country and am actually able to recharge the device. All manuals are written in some nordic language, Swedish I guess, but since I own a Nokia E71 myself with basically identical menus, I didn’t really need manuals. The other problem was that all Nokia Maps licenses were limited to Scandinavian countries too, which doesn’t help a lot when you want to test the application in Central Europe. A quick email fixed the problem. Good.
The device itself has a Navigator button which loads the map application immediately. Positioning works very fast, it instantly had me located on the map and the cartography looks very good at a first glance.
One annoying thing is that the back cover, where battery and SIM are hiding, opens really hard. “Aufquan” would be the best Austrian term to describe the process of simultaneously pushing and pulling the button with a pen or knife, which supposedly should release the back cover. I’m using my own SIM from my cell phone and need to change it frequently in order to try the 6210 Navigator. So that’s a small problem I have with the device.
Full disclosure:
Why I’m doing it?
Because I like maps, gadgets and was curious about Nokia Maps 3.0. I guess I’m not hard to convince when asked to play around with some tech toy for two weeks.
What does WOM World / Nokia get out of this?
Some backlinks, little buzz and maybe some useful feedback.
Norc, a Romanian company, is providing “street-level imaging” a.k.a. Street View for selected Central and Eastern European countries:
According to their website, the current coverage includes:
The interface is compared to Google’s Street View still a little rough around the edges, but otherwise, Norc did a fantastic job!
However, it would be interesting to know if Norc has developed its own business model based on their Street View services, and how it would work, or if they are just preparing to become the next Google snack.
[via Helge.at]
That’s pretty exciting: just came back to Vienna, spent the morning poking around in OSM and the OSM wiki to figure out who the mappers are and if there are any community activities planned and ended up reading a press release saying that Vienna is completed in OpenStreetMap.
Awesome! Big kudos to the local mapping community! The quality of the map is impressing!
As for the rest of Austria, there is a huge data import going on since Fall ‘08. More information on the process you’ll find at the wiki page. People all over Austria with good local knowledge are needed to support the import process, help identify errors and improve OpenStreetMap in rural areas.
If you want to make your town visible in OpenStreetMap, sign up and start mapping. It’s very easy and can be done using nothing more than an internet browser. Even better: spread the word, host a Stammtisch, tell your neighbors about OpenStreetMap and create your own map of your village.
For interested people in and around Vienna, the next Wiener OSM-Stammtisch is scheduled for Friday Jan 23rd ‘09, 2pm, at the Metalab.
…is something you may consider turning off if you’re unhappy with VMware Fusion’s performance.
As for ArcGIS Desktop, it works noticeable faster in VMware Fusion (aff link) if the entire workspace is moved inside the VMware image instead of accessed via “Shared Folders”. ArcMap feels snappier and geoprocessing runs about 35% faster as my quick benchmark showed. Performance issues caused by “Shared Folders” is mentioned at an ESRI Discussion thread too.
My benchmark test was just a geoprocessing task I needed to do for a project, executed in 3 different workspace environments:
#1 – inside the VMware image
#2 – on an external USB harddisk, mounted in Windows
#3 – on an external USB harddisk, mounted in Mac OS X and accessed through VMware Fusion’s Shared Folders feature
The task was to intersect 2 layers, everything done inside a File Geodatabase:
Layer A: 11,932 features (20,4361 vertices)
Layer B: 3,100 features (arcs from point buffering)
The intersect-process returned a 300MB feature class containing 952,265 features and 5,724,810 vertices. Below is the chart showing the time needed to complete the task for each workspace environment.
ArcGIS geoprocessing task performance in different workspace environments
In figures, option #1 took 8 minutes 57 seconds, option #2 9 minutes 3 seconds and option #3 needed 13 minutes 29 seconds to finish.
Clearly, the performance bottleneck in VMware Fusion is “Shared folders”. No doubt, it’s a handy feature and makes file sharing between host and guest-OS very easy, but for performance reasons you better turn it off.
Once in benchmarking-mood I ran the same task with increased memory and 2 CPUs. Out of curiosity, just to see the effect of more memory and CPU power. My standard setting for VMware Fusion is 1 CPU and 512MB RAM allocated to the guest-OS, which turned out to be the best setting for working at decent speeds in both host and guest-OS so far. The result for the same geoprocessing task with 2 CPUs and 1024MB RAM was 8 minutes 17 seconds. Little faster, but, because of experiencing a sluggish host Mac OS X, not worth it.
Despite performance I ran into another problem with “Shared Folders” and File Geodatabases a while ago. Well, I actually never verified that this problem is related to “Shared Folders”: a File Geodatabase corrupted while executing “compact database” in a “Shared Folder” workspace. According to that thread at ESRI it happened on network drives too. However, I experienced it only in “Shared Folders”, not in other workspace environments. Quite annoying bug though.