Monday, April 30, 2007

BlueSky Positioning Helps Operators Benefit From New Emergency Call Legislation

location based services

Berlin, Germany - 26th April 2007: Start-up company BlueSky Positioning is set to help mobile operators meet new European Union emergency call legislation, and could also help realise the promise of location-based services (LBS) across the wireless industry. Launching today, BlueSky Positioning’s new approach incorporates a highly accurate GPS receiver and proprietary antenna into the SIM card, which provides the opportunity to deploy precise, legally-mandated positioning capability quickly and cost-effectively across all mobile handsets.Following publication of a significantly strengthened EU directive, expected later this year, EU member countries will have just 18 months to implement a law requiring operators to identify the precise location of callers to the E-112 emergency services, potentially to an accuracy level of just a few metres. Similar to the E-911 legislation in the US, the new law is designed to improve emergency services’ reaction and response times due to improved location accuracy and therefore increase levels of public safety. However, over 50 per cent of emergency calls in the EU are made from mobile phones – and current network-based positioning technologies on the market cannot provide the degree of accuracy required.Enabling high-accuracy location technology could be an enormous challenge for operators - there are 500 million mobile phone users in the EU. To comply with this legislation would mean a massive handset upgrade programme – a hugely expensive and complicated task.BlueSky Positioning has developed patent-pending technology and processes to embed Assisted Global Positioning System (A-GPS) capability in the SIM card (USIM in the case of 3G handsets), with minimal impact on signal strength and battery life. This means that operators need only replace the SIM cards, not the phones themselves – a far more manageable solution.BlueSky Positioning’s A-GPS SIM uses an assistance data server in the mobile network to reduce the location identification time (Time To First Fix) and increase accuracy, particularly within buildings and densely populated areas. By embedding this accurate location capability in the end-user (U)SIM, SIM card manufacturers can enable swift and effective rollout and compliance – and faster emergency response times.The A-GPS SIM can also enable the delivery of a whole new set of location-based services to the consumer without compromising their privacy. Operators can quickly build critical mass and benefit from the full revenue potential of accuracy-based LBS applications such as navigation, tracking, routing, personal security, and zone-based billing.Risto Savolainen, BlueSky Positioning CEO, said “The LBS market has promised much and delivered little. This strengthened EU legislation to enhance public safety services will also catalyse the LBS market by putting the means of access into the hands of every user. Working with SIM card manufacturers, BlueSky Positioning enables mobile operators to embed the service in every consumer’s SIM and USIM card, without compromising the existing levels of card security and privacy protection.“A new handset costs anywhere between €100 and €500 plus. A replacement (U)SIM is a tiny fraction of the cost. It’s a much smaller price to pay for better safety and the opportunity for a whole new range of applications.” About BlueSky PositioningBlueSky Positioning Ltd (UK) was founded in 2005 to develop and market new generation accurate and reliable positioning technology and services specifically designed for GSM and 3G mobile phones. BlueSky Positioning has a research and development facility in Sophia Antipolis, South of France. Additional information about the company is available at www.blueskypositioning.com
NAVTEQ TRANSPORT Selected by Maptuit for Use in NaviGo(TM)

target="_blank">INDIANAPOLIS, April 30 -- NAVTEQ (NYSE: NVT), a leading global provider of digital map data for location-based solutions and vehicle navigation, announced today from the National Private Truck Council (NPTC) 2007 Education Management Conference and Exhibition that it has been chosen by Maptuit to supply NAVTEQ TRANSPORT(TM) truck attributes for their latest fleet navigation product, NaviGo. NaviGo features real-time mapping and navigation; commercial-grade routing and re-routing; text-to-speech turn-by-turn directions; and a large moving map format as well as a truck-specific dynamic road network.NAVTEQ TRANSPORT, in conjunction with NAVTEQ(R) map data, provides road attributes that directly affect truck routing. These attributes include legal restrictions, physical restrictions and preferred truck routes. As an example, the detailed data included in NAVTEQ TRANSPORT allows fleet operations to route trucks away from low-clearance areas and streets in which trucks cannot maneuver, helping to reduce incidents and minimize out-of-route miles. Furthermore, by matching routes to road-network reality, NAVTEQ TRANSPORT enables the development of applications that support more accurate route calculations."Maptuit's routing capabilities have been demonstrated repeatedly through rigorous tests and trials, with customers ultimately selecting Maptuit as the best solution for their companies. One of our routing solution strengths relies on accurate and reliable digital map data, which we obtain from NAVTEQ. We sought to collaborate with NAVTEQ because of its best-in-class approach to our solutions," said Jeff Papows, Ph.D, President and CEO, Maptuit."NAVTEQ is extremely excited to be associated with the best navigation product commercially available for large Class 6-8 trucks," said Roy Kolstad, Vice President and General Manager -- Enterprise, NAVTEQ. "The combination of NAVTEQ's fresh map data and Maptuit's innovative, robust routing application is a tremendous win for commercial fleets."NAVTEQ is showcasing its NAVTEQ TRANSPORT dataset at the NPTC 2007 Education Management Conference and Exhibition in Indianapolis, booth #511, at the Indiana Convention Center from April 29 through May 1, 2007. Maptuit NaviGo will also be demonstrated within the booth. About Maptuit CorporationFounded in 1999, Maptuit Corporation, headquartered in Burlington, Massachusetts, provides truck specific, real-time, turn-by-turn directions and navigation solutions for the trucking industry, and tracking and traffic services for the transportation and consumer markets. With Maptuit's advanced real-time web services and patented technology, companies benefit from the ability to easily look up addresses, create maps, perform proximity searches, generate optimized routes and provide directions. For more information please visit http://www.maptuit.com.About NAVTEQNAVTEQ is a leading provider of comprehensive digital map information for automotive navigation systems, mobile navigation devices, Internet-based mapping applications, and government and business solutions. NAVTEQ creates the digital maps and map content that power navigation and location-based services solutions around the world. The Chicago-based company was founded in 1985 and has approximately 2,800 employees located in 167 offices and in 28 countries.
Navizon is a software for Pocket PC or Cellphone (Windows Mobile or Symbian), that will display your location on a map

location based services


and help you find stuff around you.Navizon comes with very cool features such as the Groups, the Geotags, the Buddy Tracker and the Local search (read more about it below).
All you need to be able to use Navizon is a Pocket PC, a Smartphone or a Cellphone running with Symbian, a GPS device is optional, if you don't have any you can buy our Virtual GPS for only $24.99.

With Navizon, you can create or join groups and display the current location of the members of those groups (buddytracker) or see their Geotags.This feature can be useful in many situations: to find were your Friends are, for social networking, to help you find a cab…the only limit to the use of Navizon's groups is your imagination!
Example: the cab finderUnless you live in New York City, you must have been desperately looking for a cab at least once in your life…but this won't happen again thanks to Navizon. The concept is fairly simple, let's say a group called "find a cab" gathers taxi drivers and people who need a cab where taxi drivers send their location. Next time you are looking for a cab, you can display them members of this groups and the closest taxi driver will be displayed on Navizon. And with the click-and-call feature, you can call him and ask him to pick you up.
Create, edit, join or leave groups in Navizon's member section:
go to your member section, log in and go to the group section.

How to Geotag Photographs on the Nokia N95 for Google My Maps and Flickr

location based services

Its taken a bit of time to work this one out but with a few simple steps you can capture geotagged photographs on your Nokia N95, upload to Flickr and then add them to Google's My Maps.The process is simple:Initial Set Up1) First off go to ShoZu.com - Shozu is freely available software that allows you to both geotag photographs on your N95 and upload to a number of online services, in our case Flickr.Sign up with the site and select the Nokia N93 as your phone (the N95 is not yet listed). You will be asked to set up a user name and password as well as your mobile number. Once registered ShoZu will send a text along with a link to download the software. We downloaded via a Wi-Fi link to make sure we didn't incur any phone charges;2) Install ShoZu on your N95 and login to your account using the username and password you set up. This will authenticate your account allowing you to log back into the web based service and set up a number of destinations to upload your photographs;3) To enable uploading to Flickr go to the web page and selecting the 'Share It' tag. Now simply go through the process of allowing ShoZu the required rights to upload to your account.This completes the set up ShoZu in terms of services, we now simply need to turn on GPS tagging;4) Open ShoZu on your N95 and go to: Options/View and then the images tag which is indicated by a film strip icon. The 4th option is GPS Tagging, switch this to On.Capturing and Uploading1) Open either Nokias 'Maps' or the 'Sports Tracker' application and make sure you are getting a GPS fix, we use Sports Tracker as it allows us to additionally upload our route to Google Earth/Maps;2) Start taking your pictures, with ShoZu installed each photograph will have a location tag written into its EXIF information.3) Open ShoZu and select Share-It/All files, this will display a list of your photographs. Select the image your want to upload and click Options, this displays the choice to Send to Flickr. Select send and your image will be uploaded, again we uploaded via Wi-Fi to minimise any data charges.Your images will now be available on your Flickr page and automatically geotagged. Within Flickr you can choose to view by map which opens a Yahoo Map page, we prefer Googles My Maps options:1) At the bottom of your Flickr Photos page you will see a RSS Feed Icon and the Feed link - Right click on this link and copy the link location;2) Login into your Google Maps account and paste the feed location into the search box - now add the following to the end of the paste '&georss=true' (without the ')3) Running the search will display your photographs from the N95 on Google Maps via Flickr, to add them to My Maps simple click on each icon and choose 'Save to My Maps'You can view our geotagged images from the Nokia N95 on our My Maps page.
Posted by Smithee at 11:29 AM
Labels: , , ,
Bookmark this post:
showsbtext("sbtxt" + "8102738369118243867",0)

Scrap the Map and Send Driving Directions Straight to Your Car


location based services

April 26, 2007

As the weather gradually warms up, it's the perfect time of year to take a trip. Whether you're going to the beach, or to a baseball game, you no longer have to worry about fumbling with your map, or having the wrong directions.

A new partnership between Mapquest and OnStar is making it possible to download driving directions directly into your car. All you have to do is log onto www.mapquest.com, and hit the "Send to OnStar" link after typing in your destination. It will then send the directions to your car, eliminating the need to print out the directions. OnStar's Turn-by-Turn Navigation will then get you to your destination with GPS guided voice prompts. Another innovative feature of this system is that it can save up to five destinations at a time, all of which can be ready to be retrieved from your car whenever you want.

Once in your car, all you have to do is press the white OnStar button and say "virtual advisor" and then select one of the five destinations. If you stop by along the way at a friend's house or a gas station, the system automatically recalculates and resumes where it left off.

gpicsync

( French Translation ) ( GettingStarted ) ( ScreenShots )

April 24th 07 : New version 0.91 beta released with a better picture layout in Google Earth (see ChangeLog )(Update, April 28th: Linux tar.gz available)

April 17th 07 : What to do with your geocoded pictures: Picasa to Kmz export mini-tutorial

GPicSync automatically inserts location in your photos metadata so they can also be used with any 'geocode aware' application like Picasa/Google Earth, Flickr, loc.alize.us, etc.

Features:

  • automatically geocode your photos (EXIF header)
  • use any GPS tracklog in the universal GPX format
  • create a Google Earth KML file to directly visualize the geocoded photos and track in Google Earth
  • create a Google Earth KMZ file (containing your geolocalized pictures and tracklog).
  • add additional geonames and 'geotagged' metadata (for automatic tagging in Flickr for example)
  • rename your pictures with their date and location
  • handy tools integrated (Time correction, EXIF reader, GPX inspector, etc)

Ready to geocode your photos? GettingStarted

GPicSync stands for G:GPS Pic:Pictures Sync:Synchronization and is a Free and Open Source tool.

If you find it useful please tell others about it. If you encounter any problems, have questions, feature requests, etc, please don't hesitate to use the dedicated Google Group.

Few examples of pictures geolocalized with GPicSync:

Thanks for all the contributions and feedback.

BlueSky Positioning’s product, A-GPS SIM, is the world’s first Assisted-GPS module for SIM cards.


Together with GSM or 3G phones, it forms a complete network assisted GPS receiver capable of locating the handset quickly and accurately.

The A-GPS SIM card complies with GSM and 3G standards and thus works with legacy GSM and 3G handsets without the need for modifications or additional software.

The A-GPS SIM exploits a major technology breakthrough made by the company, including a proprietary In-SIM antenna (patents pending).

No software or hardware changes are needed for legacy handsets. The A-GPS SIM supports E-112 and E-911 Emergency Call Positioning and enables SIM, Mobile and Network based LBS applications. It’s faster, it’s targeted, and it costs the operator a small fraction of the cost of a new handset.

BlueSky Positioning’s A-GPS solution for (U)SIM appears as a SIM/USIM Toolkit application, providing remote positioning support and enabling mobile operators to provide emergency call location information to meet the EU legislation rapidly and economically, as well as providing the capability for commercial LBS applications.

A-GPS SIM also enables operators to introduce new value-added services for the mass market based on A-GPS without waiting for mass market deployment of A-GPS handsets. At the same time operators can build critical mass for LBS applications, creating services to differentiate and deliver new services and create revenue streams.

© Copyright 2007 BlueSky Positionin

Welcome to BlueSky Positioning

At BlueSky Positioning we are approaching the established mobile positioning market from a very different perspective. By addressing the key barriers of poor accuracy and high cost, we are developing solutions to enable mobile operators to deliver both mandatory and commercial location-based services (LBS) applications. BlueSky Positioning is the only company with the expertise and technology to incorporate satellite positioning capability into the SIM card. Our goal is to be the catalyst for the mass market uptake of location-enabled mobile communications.

About UsAbout the Company

BlueSky Positioning Ltd (UK) was founded in 2005 to develop and market new generation accurate and reliable positioning technology and services specifically designed for GSM and 3G mobile phones. More

ProductsProducts

BlueSky Positioning’s product, A-GPS SIM, is the world’s first Assisted-GPS module for SIM cards. Together with GSM or 3G phones, it forms a complete network assisted GPS receiver capable of locating the handset quickly and accurately. More

© Copyright 2007 BlueSky Positioning Lt

During my daytime job, I have stumbled across many definitions of what’s a Location Based Service and what’s not - most of them including the requirement that in order to qualify as ‘location based’, the service must determine the user’s location automatically in some way, e.g. via the mobile network operator, a GPS device, known locations of nearby radio (WiFi, Bluetooth) or Infrared beacons, etc.

Meanwhile, there’s lots of examples of location-specific services out in the wild that don’t use positioning technology at all: instead, users just type in zip codes or street addresses. Just check out Yahoo! Local or Yelp, some of the social LBS I covered in a previous post, or - let’s not forget ;-) - my own project, FONFinder! Hell, I can even type ‘pizza near mariahilferstr. austria‘ into Google nowadays and it will return a list of pizza restaurants in the center of Vienna. Dead simple. And definitely able to elegantly (and robustly) answer those questions that are typically associated with ’standard’ LBS scenarios: ‘Where is the next restaurant?‘ or ‘Where is the next pharamacy?‘ (Ok… at least that’s what people considered LBS in the early days, in the late 90’s. Nowadays that has, of course, been replaced by ‘Where is the next Starbucks?‘. But, hey, wouldn’t the answer to that question always be ‘just around the corner‘?)

I think it’s definitely justified to call these services ‘location based’. Ok, there’s the drawback of the user having to type - which can be annoying on a mobile phone - and having to know the street address. But it should always be possible to find a street sign somewhere…

On the positive side, it could be argued that these low-tech LBS don’t suffer from the same inherent privacy problem as their ‘true’ LBS counterparts - because the system has no way of telling whether users aren’t actually lying about their location (which, I think, is an important aspect!)

Anyways - the recently hyped social messaging service twitter is a particularly intriguing example of a service that includes such low-tech LBS functionality. I’m not gonna explain it in lengthy words now - just check out twittervision and you’ll see what I mean. (Watching the world map scroll as the messages come in has something almost hypnotic to me :-D )

What has really opened my eyes about LBS and twitter, however, was a recent blog post by Stefan Geens of Ogle Earth, commenting on mologogo’s twitter integration and (here it is again) my FONFinder (thanks, Stefan!!): Not only does twitter feature an open API that allows Web services to react to twitter messages; but also, first applications are now becoming available that link twitter to GPS - just as mologogo is doing it! (Check out thilo’s post at ‘Das Zentralorgan’, for an additional example.)

My personal bottom line is: with it’s simple interface (SMS) and basic functionality, twitter could turn into the perfect middleware/ecosystem for those basic ‘Where is?’-type of location based services. To practice what I preach, I’ve decided to follow Stefan’s suggestion :-) I’m building a twitter interface for the FONFinder. The goal of this being that you will (eventually) be able to tweet something like ‘d fonf l:mariahilferstr.,austria’ or ‘d fonf l:48.232,16.411′ (with nothing preventing you from taking these coordinates directly from a GPS) and get the street address and distance of the nearest Fonspot SMSed back to you. That’s it.

Wow. That’s my longest post so far. And you’re still reading it! Thanks! ;-)

Location-Based Services

What Are Location-Based Services?

Location-based services (LBS) are applications that leverage the user's physical location to provide an enhanced service or experience. Location awareness can be used, for example, for navigation and mapping, workforce tracking, finding points of interest, and getting weather information. It presents a compelling new business opportunity for application developers, operators, and content producers. Location awareness differentiates mobile applications from traditional PC and wired Internet services.

The S60 platform offers developers easy-to-use APIs and ready-made user interface components to make mobile applications location-aware. Additionally, starting with S60 3rd Edition, the Location Acquisition API is also supported via JSR-179, the Location API for the Java™ 2 Platform, Micro Edition (J2ME™).

From S60 3rd Edition, Feature Pack 2 onwards, Map and Navigation Framework is provided for easy map data access, creating lucrative new business opportunities for third-party applications.

To learn more how you can capitalize on location-aware applications, please take a look at our LBS White Paper.

The following table provides you an overview of the availability of LBS features in different platforms and devices.

Platform

LBS Features

Featured Devices

S60 2nd Edition,
Feature Pack 1

Support for MT-LR Privacy

Nokia 7610

Nokia 6670

Nokia 3230

Nokia 6260

S60 2nd Edition,
Feature Pack 2

Support for MT-LR Privacy,
Location Acquisition API

Nokia 6630

Nokia 6680

Nokia 6681

Nokia 6682

S60 2nd Edition,
Feature Pack 3

Same as in FP2

Nokia N70

Nokia N72

Nokia N90

S60 3rd Edition

Same as in S60 2nd Edition, FP2 and FP3

Location Acquisition API (updated),
Landmarks API,
Landmarks Search API,
Landmark Database Management API ,
Landmarks UI Add/Edit API,
Landmarks UI Selector API,
Satellite Info API,

JSR-179

Nokia 3250

Nokia 5500

Nokia E50

Nokia E60

Nokia E61

Nokia E62

Nokia E70

Nokia N71

Nokia N73

Nokia N75

Nokia N80

Nokia N91

Nokia N92

Nokia N93

S60 3rd Edition Feature Pack 1

Same as in S60 2nd Edition, FP2 and FP3

Location Acquisition API (updated),
Landmarks API,
Landmarks Search API,
Landmark Database Management API ,
Landmarks UI Add/Edit API,
Landmarks UI Selector API,
Satellite Info API,

JSR-179

Nokia N95, Nokia E90 Communicator

Java™ 2 Platform, Micro Edition (J2ME™).

Java Location API (JSR-179)

Nokia 6265

Nokia 6265i

Nokia 6165

Nokia 3250

Nokia E60

Nokia E61

Nokia E70

Nokia N71

Nokia N80

Nokia N91

Nokia N92

Series 80
2nd Edition

Location Acquisition API

Nokia 9300

Nokia 9300i

Nokia 9500

Other

Support for MT-LR Privacy

Location Acquisition API,
Landmarks API,
Landmarks Search API

Nokia 7710

Supported location technologies

Technology

Devices

Integrated GPS Nokia N95, Nokia E90 Communicator

Bluetooth GPS (external)

Nokia 6265

Nokia 6265i

Nokia 7610

Nokia 6670

Nokia 3230

Nokia 6260

Nokia 6630

Nokia 6680

Nokia 6681

Nokia 6682

Nokia N70

Nokia N90

Nokia N92

Nokia 3250

Nokia E60

Nokia E61

Nokia E70

Nokia N71

Nokia N80

Nokia N91

Nokia 9300

Nokia 9500

Nokia 7710

Network-based positioning

Nokia 3250

Nokia E60

Nokia E61

Nokia E70

Nokia 7710

What's New in S60 3rd Edition - the Landmark APIs

A landmark is a representation of a geographical location and thus landmarks, or Points-Of-Interests (POIs) as they are also known, are an integral part of almost any location-aware application. The new landmark functionality in S60 3rd Edition enables applications that allow end users to create landmarks for their favorite places, send landmarks to their friends, navigate to a landmark, and of course to manage their collection of landmarks.

S60 3rd Edition includes a dedicated application for the centralized management of user landmarks. Thus it is not necessary for the application developers to put their effort in constructing such a system. Instead, developers are free to concentrate on how they would like to use landmarks in their own applications.

As you can observe from the preliminary screenshots, the user can access landmarks either directly or hierarchicly via categories.

To learn how to take advantage of landmarks in your application, please have a look at the Landmarks API, the Landmarks Search API, the Landmarks Database Management API, and the related example application source code. JSR-179 can be used to access landmarks from Java MIDlets.

See also the Landmarks Exchange Format Specification for details about how the landmarks can be represented in XML format and as such exchanged between mobile devices (through local connectivity) or between content providers and their mobile users (for example, through Web sites). See the Landmarks Exchange Format XML Schema for automated landmark files validation.

What's New in S60 3rd Edition - the Landmarks UI Add/Edit Component API

If your application creates new landmarks, it is likely that your application will need to prompt the end user for some additional information about the landmark, for example, how he or she would like to name or categorize the landmark. This usage scenario is likely to be so common that we included a ready-made UI component in S60 3rd Edition to do just that. The component also does the coordinate acquisition via the Location API.

You can also use the component in view only mode if you wish to show the details of a certain landmark to the end user and want to avoid the possibility of the end user modifying the landmark in any way. To learn more about this ready-made UI component, please have a look at the Landmarks UI Add/Edit API and the source code of the related example application in the S60 3rd Edition SDK.

What's New in S60 3rd Edition - the Landmarks UI Selector Component API

Many times your application will need the end user to indicate one or more landmarks for you, for example, for your application to show the indicated landmark(s) on a map or provide navigation guidance to them. To help you with that, S60 3rd Edition includes a ready-made UI component that you can use to prompt the end user for one or more landmarks or for one or more landmark categories.

Simply launch the UI component and you will get the landmarks or categories selected by the end user as return values. The UI component takes care of all the required end-user interaction. For more details, please see the Landmarks UI Selector API and the source code of the related example application.

What's New in S60 3rd Edition - the GPS Satellite View

Every decent location-aware application has a GPS satellite view, right? Now wouldn't it be a drag if every developer would need to make their own satellite view? And wouldn't it be a pain for end users to try to cope with different-looking views that are supposed to depict the same thing, the availability of the GPS satellites?

To answer these questions, S60 3rd Edition offers developers a ready-made UI component that applications can use to display GPS satellite availability in a clear and coherent way. To learn how easy it is to embed the satellite view into your application, please have a look at the Satellite Info API and the source code of the related example application.

Make Your Application Location-Aware - Now and with Ease

The Location Acquisition API enables native Symbian OS applications to determine the current location of the handset. This API provides easy access for determining a user's current location, independent of the positioning technology being used. This means that applications can utilize all available positioning technologies, such as Bluetooth Global Positioning System (GPS) accessories and network-based positioning, via a single API.

To make your mobile application location-aware, more information is available in the Location Acquisition API and the source code of the related example applications.

Testing Made Easy

Developing location-aware software can be tedious if you need to transfer your application to a mobile device and start walking or driving around to test the effects of your latest changes. To overcome this problem, the S60 platform allows you to create a text file from which the positioning system will fetch coordinates, thus simulating the device moving along the given path.

First prepare a simulation data file. For details, please take a look at the Simulation PSY User Guide.

Then tell the positioning system the location of your simulation data file. In S60 releases prior to 3rd Edition, this happens with a separate SimPsyConfigurator application that is available in the application grid.

Starting from S60 3rd Edition, you can set the simulation data file from the settings of the Simulation positioning method.

Also make sure that the Simulation positioning method is the selected positioning method when testing. You can check and alter this setting using the Location Settings application.

For more information, please have a look at the Simulation PSY Configurator User Guide and the Simulation PSY User Guide.

Handset Support for Network-Resident LBS

Starting from S60 2nd Edition, Feature Pack 1, MT-LR Privacy messages from network-resident LBS applications are supported. MT-LR is an acronym for Mobile Terminated Location Request and is also known as LCS Location Notification. These messages let the device owner decide if a network-resident LBS application, such as a weather service, may use the device’s location to provide the service requested by the device owner. For more information on the role of LCS Location Notification in Location Services, please refer to 3GPP TS 23.271 (or 03.71). For signalling protocol level information of LCS-LocationNotification, please refer to 3GPP TS 24.030 (or 04.30)."

AGPS Measurement Engine Interface (MEIF)

The AGPS Measurement Engine Interface (MEIF) Specification describes a standard interface that can be used in a setup where the measurement and position-calculation parts of the GPS or AGPS are separated into different devices that can be implemented separately. For more information, see the MEIF Specification description.

Tools

S60 Platform SDK's for Symbian OS, for C++
S60 Platform SDK for Symbian OS, for C++ allows C++ developers to quickly and efficiently run and test applications for devices that are compatible with the S60 Platform.

Series 80 Platform SDK's for Symbian OS, for Java
The Personal Profile SDK is the kit for developers creating Java™ Personal Profile applications for Nokia platform devices. The product consists of a phone emulator, application programming interfaces (APIs), documentation, and examples.

Series 80 Platform 2.0 SDK for Symbian OS, for MIDP enables Java™ 2 Platform, Micro Edition (J2ME™) application development for devices based on Series 80 Platform 2.0, and is compatible with the Nokia 9300 smartphone and Nokia 9500 Communicator.

Nokia Prototype SDK 2.0 for Java™ 2 Platform, Micro Edition
Nokia Prototype SDK 2.0 for J2ME™ enables developers to quickly and efficiently run and test applications for devices compatible with the Series 40 Platform, the Series 60 Platform, and the Series 80 Platform, as well as for the Nokia 7710 widescreen smartphone, before the final SDKs become available.

Documents

16-Apr-2007

Series 40 Platform: Introductory White Paper v2.2
This document provides an overview of the Series 40 platform and introduces Java™ technology and media development for it.

03-Apr-2007

C++ Developer's Library (online)
The C++ Developer's Library is an integrated package for developers wishing to develop S60 C++ applications. This first version focuses on getting started information, application framework and UI. The library also contains the complete S60 API reference and links to the Symbian OS online library, as well as to code examples and documents available on Forum Nokia. The library describes S60 3rd Edition and S60 3rd Edition FP1 implementations of the C++ technology. The library is available in three formats, this is the online version. We recommend that you use Mozilla Firefox or Netscape to view the library. There may be performance issues when using Microsoft Internet Explorer.

03-Apr-2007

C++ Developer's Library (stand-alone)
The C++ Developer's Library is an integrated package for developers wishing to develop S60 C++ applications. This first version focuses on getting started information, application framework and UI. The library also contains the complete S60 API reference and links to the Symbian OS online library, as well as to code examples and documents available on Forum Nokia. The library describes S60 3rd Edition and S60 3rd Edition FP1 implementations of the C++ technology. The library is available in three formats, this is a stand-alone version. Extract the .zip file to any folder on your computer, and click eclipse.exe to start the application.

03-Apr-2007

C++ Developer's Library (Eclipse plug-in)
The C++ Developer's Library is an integrated package for developers wishing to develop S60 C++ applications. This first version focuses on getting started information, application framework and UI. The library also contains the complete S60 API reference and links to the Symbian OS online library, as well as to code examples and documents available on Forum Nokia. The library describes S60 3rd Edition and S60 3rd Edition FP1 implementations of the C++ technology. The library is available in three formats, this version can be integrated into the Eclipse help.

06-Feb-2007

Java™ ME Developer's Library v1.2 (Online)
This Developer's Library is a complete resource package with introductory, getting started, tutorial, and API level information for developers wishing to use the S60 or the Series 40 platforms for developing mobile Java applications or services. The library describes S60 3rd Edition, FP1 and Series 40 3rd Edition, FP2 implementations of the Java technology and API specifications. The information is to a large extent valid also for earlier platform releases (the differences are described in the Implementation notes section). This updated version of the library includes, for example, new Developer's Guides for Advanced Multimedia Supplements API, SATSA-PKI API, and SATSA-APDU API. The library is published in three formats. This is an online version.

06-Feb-2007

Java™ ME Developer's Library v1.2 (Stand-alone)
This Developer's Library is a complete resource package with introductory, getting started, tutorial, and API level information for developers wishing to use the S60 or the Series 40 platforms for developing mobile Java applications or services. The library describes S60 3rd Edition, FP1 and Series 40 3rd Edition, FP2 implementations of the Java technology and API specifications. The information is to a large extent valid also for earlier platform releases (the differences are described in the Implementation notes section). This updated version of the library includes, for example, new Developer's Guides for Advanced Multimedia Supplements API, SATSA-PKI API, and SATSA-APDU API. The library is published in three formats. This is a stand-alone, downloadable version.

06-Feb-2007

Java™ ME Developer's Library v1.2 (Eclipse plugin)
This Developer's Library is a complete resource package with introductory, getting started, tutorial, and API level information for developers wishing to use the S60 or the Series 40 platforms for developing mobile Java applications or services. The library describes S60 3rd Edition, FP1 and Series 40 3rd Edition, FP2 implementations of the Java technology and API specifications. The information is to a large extent valid also for earlier platform releases (the differences are described in the Implementation notes section). This updated version of the library includes, for example, new Developer's Guides for Advanced Multimedia Supplements API, SATSA-PKI API, and SATSA-APDU API. The library is published in three formats. This version can be integrated into the Eclipse help.

28-Nov-2006

AGPS Measurement Engine Interface (MEIF) License Agreement
The AGPS Measurement Engine Interface (MEIF) Specification describes a standard interface that can be used in a setup where the measurement and position-calculation parts of the GPS or AGPS are separated into different devices that can be implemented separately. This agreement grants a license to utilize AGPS MEIF.

07-Nov-2006

S60 Platform: BLID Application Satellite Info API Specification v1.1
This updated document specifies the BLID Application Satellite Info API, which is used to indicate satellite data availability and quality. The interface basically displays a dialog that lists the satellites available with their corresponding signal strengths. The BLID Application Satellite Info API is available in S60 3rd Edition and onwards.

03-Nov-2006

MIDP: Location API Developer's Guide v2.0
This updated document describes the Location API for Java ME (JSR-179), which enables the development of location-based mobile applications. The three main features that the Location API brings to mobile programming are obtaining device location information, the possibility to create, edit, store, and retrieve landmarks, and the possibility to obtain device orientation information. This document also describes and illustrates the architecture of MIDP: Location API Example - Tourist Route.

29-Aug-2006

S60 Platform: Landmarks UI Add/Edit API Specification
This document specifies the Landmarks UI Add/Edit API, which is available from S60 3rd Edition onwards. The API provides UI components for creating and manipulating landmarks.

29-Aug-2006

S60 Platform: Landmarks UI Selector API Specification
This document specifies the Landmarks UI Selector API, which provides an interface to applications for listing and selecting one or more landmarks or categories, which exist in the landmark database. This interface allows displaying a dialog, listing all the landmarks or categories, where the user can select one or more landmarks or categories. The Landmarks UI Selector API is available from S60 3rd Edition onwards.

31-Mar-2006

JSR 179 Location API for J2ME™version 1.0.1 - HTML javadoc version
This is the Final Release version of the JSR-179 Location API for J2ME specification developed under the Java Community Process. This specification defines a J2ME Optional Package that enables mobile location-based applications for resource limited devices. The API is designed to be a compact and generic API that produces information about the present geographic location of the terminal to Java applications.This API covers obtaining information about the present geographic location and orientation of the terminal and accessing a database of known landmarks stored in the terminal.

11-Nov-2005

S60 Platform: Landmarks API Specification
This document specifies the Landmarks API, which is available from S60 3rd Edition onwards. The API allows terminal applications to manage landmarks in a consistent way. For instance, a landmark received in an e-mail may be stored so that it is available for a map application. Revision on August 29, 2006: minor editorial changes.

01-Sep-2005

S60 Platform: Landmarks Exchange Format Specification
This document specifies how mobile applications can exchange landmark information over cellular and local connectivity, supported from S60 3rd Edition onwards. The document also contains use cases and examples. Revision on August 29, 2006: minor editorial changes.

28-Apr-2005

Consumer Applications - Spring 2005 (7.8mb)
Low resolution (7.8mb) version of the Forum Nokia Spring 2005 Consumer catalog. Includes Addendum. Updated 4/27/05

14-Mar-2005

Capitalizing On The Location-Based Services Opportunity
This white paper presents an overview of how Nokia platforms and tools are opening the Location Based Services opportunity for developers.

11-Nov-2004

S60 Platform: Landmarks Search API Specification
This document specifies the Landmarks Search API, which is available from S60 3rd Edition onwards. The API extends the Landmarks API to enable searching for landmarks or landmark categories that match certain criteria. For instance, a client can search for all restaurants in a landmark database. Revision on August 29, 2006: minor editorial changes.

11-Nov-2004

S60 Platform: Landmarks Database Management API Specification
This document specifies the Landmarks Database Management API, which allows clients to perform database management tasks such as adding new databases or deleting existing databases. The API is available from S60 3rd Edition onwards.

11-Nov-2004

S60 Platform: Location Acquisition API Specification
This document specifies the Location Acquisition API, which is available from S60 2nd Edition, Feature Pack 2 onwards. The API allows terminal applications to retrieve information related to the current location of the mobile device.

Featured Items

Newsletter Sign Up

Privacy Policy Archives

Forum Nokia Blogs

Nokia Content Discoverer

Forum Nokia PRO

Forum Nokia Champion

Business Opportunities

Events

Press & Analysts

Application Catalogs

Forum Nokia e-store

Forum Nokia RSS feeds

  • Latest Devices
  • Latest Documents
  • Latest Tools
  • Latest Blog Entries

Send this page

Developer Feedback