GeoSmart Weblog

Just another WordPress.com weblog

What Tools Do You Need to Develop a Mobile LBS Application Part 4

A key component and possibly the second highest webmap query on the Internet is for Driving Directions and this has even more relevance in a mobile scenario. Driving Directions is a key point of difference for GeoSmart in New Zealand. In many other countries, the government provides free or low cost map data of a very high quality and suitable for car navigation and other purposes. In New Zealand this isn’t the case. The LINZ maps are the official datum for cadastral property boundaries. However, their road centreline is derived by a computation of the property boundaries.

As I’ve previously mentioned, New Zealand was town planned in Edinborough in the late 1800’s and many of the roads they draughted were never formed or constructed. They are known as paper roads. These roads exist on paper and on the LINZ map data used by services such as Google Maps, but they physically don’t exist. An example is Threepwood Road in Otago. If you have a look on the hybrid mode of satellite view and map view on Google, you will see that while the road exists on the map data, it physcially isn’t there in the satellite photography. This would cause a real problem if you wanted to go for a drive on it.

When GeoSmart discovered this problem and realised that, while it didn’t matter a lot for printed maps where you still have to analyse the data and make a decision on where you drive yourself, practically speaking, if you used either car navigation or a printed set of directions and couldn’t see a map as such, paper roads could cause a lot of confusion and grief. With LINZ having the only full maps of New Zealand, we decided we had to make our own maps. To do this we drove almost every road in New Zealand and also used a lot of Orthophotography to develop a driven road centreline, eliminating all paper roads and at the same time creating an accurate road centreline.

While collecting this data, we were also able to collect information such as the intersections controls (roundabouts, traffic lights etc), turn restrictions (one way streets, no left turns), speed zones, whether the road was sealed, accuracy of street signs and much more. We were even able to establish things like the angles of corners and inclination of roads (how steep they are etc).

This enabled us to build the car navigation dataset used by all the major brands including TomTom, Navman, BMW, Ford, Siemens VDO etc. It also allowed us to create sites like AA Maps and provide the API’s used on Wises web site. Now you can go to AA Maps, plan your journey and print out turn by turn directions from anywhere in NZ to anywhere in NZ and be confident that the instructions will work.

So, from there to your mobile. The Directions Web Service will work on any device that can identify a start point and where the user wants to go. The User Interface is up to the developer  and will probably vary from phone to phone because of its controls and screen size. For example a touch screen such as that on the iPhone or Windows Mobile, would have functionality closer to a web page, whereas a phone without a touch screen would have to function differently. That is really just a design issue, not a significant barrier.

If your phone has GPS or the ability to use cell tower triangulation, it will know where it is. But it is also possible (if you know) to tell your mobile where you are and where you want to go This could be an address you want to get directions to, or it could be Points of Interest from our POI Web Service mentioned in Part 2 of this series. Once you know the start and end of your journey, you can use the Directions web service to guide people directly to your desired location.

So now you can have turn by turn directions delivered to your phone. This could be send as an SMS with text directions, it could be an MMS combining text directions with an image of the route map, or an image zoomed in to your destination, or it could be information in your mobiles web or WAP browser, with enanced functionality.

Here’s the thing. If you are at home or in the office, you can use your PC, but it is of no use to you in your car or away from the computer. You may not know where you are going to want to go until you are out on the road. An LBS application with the Directions Web Service can give you the same freedom, without the necessity of interpreting a map, or more commonly the map isn’t there when you need it. Pick up the kids, meet someone for coffee, find your way from the car park to the show. All easy to do with LBS.

Just as a footnote, a few days ago a 62 year old woman set of from Christchurch to her  home on the West Coast of the South Island. She didn’t arrive and her friends and family spent a couple of days searching for her after she crashed her car down a 5 metre embankment. She was eventually found but the story could have been very different. She may not have been found at all, or not until it was too late to save her life, or she could have been found very easily. If she had a mobile with GPS, after she had been reported missing, if the phone was within coverage, it could have been called and located using an LBS service using GeoSmart tools and her searchers could have had turn by turn directions on their mobiles, right to the spot where her car was.

I suspect this sort of application will be available within the next few years, but someone has to create it first. Tracking elderly people is something that is also a major opportunity.

April 5, 2009 Posted by | AA Maps, cartography, driving directions, geosmart, gps, lbs, location based services, maps, Mobile maps, navman, new zealand, new zealand maps, satnav, tomtom, web maps | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | 1 Comment

What Tools Do You Need To Create An LBS Application in New Zealand Part One

The first thing you need is a map. Many people seem to think (as I did before I joined GeoSmart) that maps are fundamentally the same and equal. Makes sense doesn’t it. We’re a small country and you would expect all maps to have the same data.

That would seem to make sense given that the core data for New Zealand is supplied by the Government under the Land Institute of New Zealand. LINZ is the authority when it comes to things cadastral. They manage land titles, topographic data about New Zealand, hydrographic information, the official street name register and is a part of the NZ Geographic Board which is currently busy deciding whether Wanganui should now be called Whanganui.

When GeoSmart decided to enter the car navigation business, we quckly found that the ‘official’ maps of New Zealand have a ‘computed road centreline’. In effect that means that they use a system which places the road notionally between property boundaries. This wasn’t a big deal when it came to road maps because a road map requires that you plan your rate based on a paper image and if it is not exactly right, you can interpret the map and get to your desired location. This data also contains ‘paper roads’. Paper roads are unformed roads that were draughted in Scotland in the late 1800’s and never constructed. Again if you were to see a road on a map and it physically isn’t there, no problem, you can work your way around it. Consumers Institute has a number of pages on this topic.

Whilst not an issue on a printed map, consider the problems if you tried to use this data for car navigation and routing. When GeoSmart made the commitment to develop a car navigation database, it was quickly realised that it was necessary to drive every road in New Zealand and also use information gleaned from its Orthophotography in order to create an accurate road centreline database. In doing so, we were also able to capture information including one way streets, dual carriageways, turn restrictions, speed zones, the actual name on the street signs (which were sometimes different to the LINZ data) whether a road was paved or not and much more. In doing this we were able to create a database suitable for car navigation (over 90% market share including TomTom and Navman)  and many other services including Fleet Management (around 80% market share including Navman Wireless, Astrata, Xlerate, Argus Tracking, Blackhawk).

Fleet management is even more critical. One of the key reasons companies buy Fleet Management solutions is because they can claim back Road User Charges (RUC) as they are not liable to pay taxes when their trucks are on private property. If they were to try to do this using the computed road centreline, they would struggle to pass a Tax Audit because using in accurate maps, they could often be calculated to be off-road, when they are actually on the road. You can best see this in evidence by using a map dataset which overlays aerial or satellite imagery with the cadastral map data set. Especially in rural areas you will find that there are major discrepancies between the photography and the map data.

So after that long journey, GeoSmart is now able to offer you access to the Web Mapping API, which can enable you to offer routing, driving directions and other tools including displaying map tiles on a mobile or PDA display. You can search for streets, numbers and businesses.

If you explore the many LBS applications being developed overseas (some of which this blog will cover in the near future, you will see that driving or turn by turn directions are a very popular feature of LBS applications. Whether it is a LBS game, a buddy finder, proximity based marketing, planning a run or cycle trip, routing has a part to play and is one of the major reasons that people internationally use LBS applications. If you don’t have a map book (we create the Wises and AA Maps you probably have in your car)  or folded map with you, you have less opportunity to interpret data that is inaccurate, so it is imperative that you use accurate information in your application.In countries where the Government provides accurate maps (such as the USA) this is very easy to do, but in New Zealand, to date only GeoSmart has a fully driven road centreline. And of course as you know from a previous blog, we are now re driving all of New Zealand in the RAPIDcV with around 20cm accuracy.

The RAPIDcV GeoSmarts hi-tech data capture vehicle

So if you want to create an application with accurate maps and directions, the SmartFind WebMap API is a key component. If you would like to check this out, we do of course have the ability to give you a Developer Agreement at no cost so that you can start creating your application.

March 31, 2009 Posted by | AA Maps, car navigation, cartography, driving directions, geosmart, gps, lbs, lbs games, maps, new zealand, proximity based marketing, satnav, tomtom, Uncategorized, web maps | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | 1 Comment

Free New Zealand web cartography tools for educational and non-commercial purposes.

Free New Zealand web cartography tools for educational and non-commercial purposes.

As the Gold Sponsor for GeoCart’2008, the National Cartography Conference at Auckland University from 1-3 September, GeoSmart Maps Ltd General Manager Phil Allen has announced that GeoSmart is offering a set of web tools for web cartographers for use free of charge for educational and non-commercial use. He will outline these in a presentation at the conference on Wednesday 3 September.

“As the leading supplier of commercial cartographic products in New Zealand, we would like to encourage development of new applications,” said Phil Allen. “There are so many opportunities for people to develop wonderful web and mobile applications and we have the API’s and web services, as well as a wealth of geo-spatial data about New Zealand. “

The tools GeoSmart is making available include:

· Web mapping API

· Points of Interest API

· Geocoding and reverse geocoding web services

· Directions API

· Route Optimisation API

· Vector Graphics API

· Map datasets (NZ map base, Cadastral map base, Census map base)

Using such tools, web cartographers can build complex web, Location Based Services (LBS) and Mobile based GIS solutions such as; Carbon footprints for businesses by measuring the journey times of staff going to and from work and including their business activities to computing calorie burn when a user creates a walk/cycle/running route. The tools include all of the APIs required and a set of maps with many code examples. Allen’s paper will present these tools and advise how educational institutes and the web cartography community at large can take advantage of these for promoting and enhancing our industry.

For more information please contact Luigi Cappel luigi.cappel@geosmart.co.nz

August 29, 2008 Posted by | car navigation, carbon footprint, cartography, driving, driving directions, gps, maps, new zealand, route optimisation | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | Leave a comment