20
Location-Based Module

This document describes the reusable Location-Based Module, included in Oracle9iAS Wireless. Each section of this document presents a different topic. These sections include:

• Section 20.1, "Location Modules"

• Section 20.2, "Driving Directions"

• Section 20.3, "The Business Directory Module"

• Section 20.4, "Maps Module"

• Section 20.5, "Extending the Mobile Modules"

20.1 Location Modules

Location-based services make mobile applications easier to use and provide them with quick access to timely and critical information.

20.1.1 Location Picker

The Location Picker module enables users to pick and manage their frequently-accessed locations. Using this module, a user can specify a location that can be used by another module, such as the driving directions module. This location can be the user's default location, the current location (if mobile positioning is enabled), a Locationmark selected by the user, a recent location used by the user, or a new location to be entered by the user

The Location Picker module is used by other modules to acquire a location from the user. When used directly by the user, Location Picker provides management of the user's locationmarks and allows the user to set his "preferred" location, which is either the user's current location (when mobile positioning is available and on) or the user's default locationmarks.

Other location modules include Driving Directions, Maps, and Business Directory. These modules use the Location Picker to acquire location(s) from the user if the user does not have a "preferred" location or if the user specifically wants to change the location used for those modules.

This module integrates with positioning servers when available and is built upon the Oracle9iAS Wireless Location Application Component API.

20.1.2 Configuring the Location Picker Module

This service requires the Oracle9iAS Wireless geocoding provider only when the geocoding of addresses is needed and the Oracle9iAS Wireless mobile positioning provider only when the positioning feature is needed. The geocoding and mobile positioning are optional features.

Table 20-1 Requirements for the Location Picker Module

Name	External Providers	Instructions	From
Geocoding Provider	otn.oracle.com	See Section 15.1.3.	2.0
Mobile positioning provider	otn.oracle.com	See Section 15.1.3.	2.0

This module does not require scripts.

20.1.2.1 Configuring the Input Parameters of the Location Picker Module

The Location Picker module includes the following input parameters:

• ORACLE_SERVICES_LOCATION_PICKER_STACKSIZE
  • Description: The depth of the location history stack. When it reaches this depth, the least recent locations are replaced by new locations to keep the depth constant.

  • Default Value: 72

• ORACLE_SERVICES_LOCATION_PICKER_RECS_PER_PAGE
  • Description: The number of locations displayed per page. Used to indicate how many locations are displayed per page.

  • Default Value: 9

20.1.2.2 Linking to the Location Picker Module

You link to the location picker module using the following virtual URL:

omp://oracle/services/location/picker - Invocation Interface

Input Parameters

The location picker has the following input call parameters:

• LOCATIONTITLE
  • Description: The name of the location to be specified. This will be displayed throughout the Location Picker module as the title of the page.

  • Valid Value: A String. For example:
    • LOCATIONTITLE=Map

    • LOCATIONTITLE=Destination Location

• LOCATIONQUALITY
  • Mandatory: No

  • Description: The quality of the location to be specified. This will be used to check if the specified location meets the required quality.

  • Valid Values:
    • 1 (Address quality)

    • 2 (Street quality)

    • 3 (Intersection quality)

    • 4 (Postalcode quality)

    • 5 (City quality)

    • 6 (County quality)

    • 7 (State quality)

    • 8 (Country quality)

    • 11 (Unknown quality)

• LOCATIONMASK
  • Mandatory: No

  • Description: The mask used to specify which location fields will be available when entering a new location.

  • Valid Value: An integer derived by bitwise ORing together the integer values for all the location fields wanted. The values are defined as follows:
    • COMPANYNAME_FIELD = 1

    • FIRSTLINE_FIELD = 2

    • SECONDLINE_FIELD = 4

    • LASTLINE_FIELD = 8

    • BLOCK_FIELD = 16

    • CITY_FIELD = 32

    • COUNTY_FIELD = 64

    • STATE_FIELD = 128

    • COUNTRY_FIELD = 256

    • POSTALCODE_FIELD = 512

    • POSTALCODEEXT_FIELD = 1024

    • LAT_FIELD = 2048

    • LNG_FIELD = 4096

    • Examples:
      
      LOCATIONMASK=14 (address line 1, address line 2, address last line)
      LOCATIONMASK=162 (address line 1, city, state)

• MOD
  • Mandatory: Optional

  • Description: This parameter is used to specify a condition on the returned location. For example, if the user only wants to choose among the named location (for example, Location Marks), then use MOD="LM". If unspecified, the default mode will be used (for example, all available locations will be offered as choices).

  • Valid Value: LM (Allows to choose among existing Location Marks or create new ones.)
    
    Example: MOD=LM

Output Parameters

The output parameters for the Location Picker module include the following:

Table 20-2 Output Parameters of the Location Picker

Parameter Name	Mandatory	Description	Valid Value
CN	No	Company Name	A string. For example: CN=Oracle Corp.
FL	No	Address First Line	A string. For example: FL=500 Oracle Parkway
SL	No	Address Second Line	A string. For example: SL=Redwood City, CA
LL	No	Address Last Line	A string. For example: LL=US
BL	No	Block	A string. For example: BL=Block 400
CI	No	City	A string. For example: CI=Redwood City
CT	No	County	A string. For example: CT=San Mateo
ST	No	State	A string. For example: ST=CA
PC	No		Postal Code A string. For example: PC=94065
PCE	No	Postal Code Extension	A string. For example: PCE=5423
CO	No	Country	A string. For example: CO=US
LT	No	Latitude	Double. For example: LT=37.2433
LN	No	Longitude	Double. For example: LN=-122.3452
N	No	Name	A string. For example: N=Golden Gate Park
LMN	No	Location Mark Name	A string. For example: LMN=Office
STATUS	No	The status of the module call.	(Ok) CANCEL (Cancelled)

20.2 Driving Directions

The Driving Directions module allows a mobile application to provide its users with driving directions between an originating address and a destination address. It links to the Location Picker module to enable users to select originating and destination addresses not provided by Driving Directions. The Driving Directions module also links with the Maps module for enhanced routing.

This module is built upon the Oracle9iAS Wireless Location Application Component API.

20.2.1 Configuring the Driving Directions

This service requires the Oracle9iAS Wireless routing provider.

Table 20-3 Requirements for the Location Picker Module

Name	External Provider(s)	Instructions	From
Routing Provider	otn.oracle.com	See Section 15.1.3.	2.0

This module does not require scripts.

20.2.1.1 Input Parameters

The Driving Directions module includes the following input parameters:

• ORACLE_SERVICES_LOCATION_ROUTER_RECS_PER_PAGE
  • Description: Items per page. Used to indicate how many steps are displayed per page.

  • Default Value: 9

• ORACLE_SERVICES_LOCATION_ROUTER_VOICETOKENFILE
  • Description: The absolute file path for the voice token file--a properties file that gives the mapping between recorded .wav files and voice outputs.

  • Default Value: .

20.2.1.2 Linking to the Driving Directions Module

You link to the Driving Directions module through the following virtual URL:

omp://oracle/services/location/directions

Input Call Parameters

The Driving Directions module includes the following input call parameters:

Table 20-4 Input Call Parameters of the Driving Directions Module

Parameter Name	Mandatory	Description	Valid Value
OCOMPANYNAME	No	Company Name of Starting Location	A string. For example: OCOMPANYNAME=Oracle Corp.
OADDRESS	No	Address First Line of Starting Location	A string. For example: OADDRESS=500 Oracle Parkway
OADDRESS2	No	Address Second Line of Starting Location	A string. For example: OADDRESS2=Redwood City, CA
OADDRESSLL	No	Address Last Line of Starting Location	A string. For example: OADDRESSLL=US
OBLOCK	No	Block of Starting Location	A string. For example: OBLOCK=Block 400
OCITY	No	City of Starting Location	A string. For example: OCITY=Redwood City
OCOUNTY	No	County of Starting Location	A string. For example: OCOUNTY=San Mateo
OSTATE	No	State of Starting Location	A string. For example: OSTATE=CA
OZIP	No	Postal Code of Starting Location	A string. For example: OZIP=94065
OZIPEXT	No	Postal Code Extension of Starting Location	A string. For example: OZIPEXT=5423
OCOUNTRY	No	Country of Starting Location	A string. For example: OCOUNTRY=US
OLAT	No	Latitude of Starting Location	(Double) For example: OLAT=37.2433
OLNG	No	Longitude of Starting Location	(Double) For example: OLNG=-122.3452
ONAME	No	Name of Starting Location	A string. For example: ONAME=Golden Gate Park
DCOMPANYNAME	No	Company Name of Destination Location	A string. For example: DCOMPANYNAME=Oracle Corp.
DADDRESS	No	Address First Line of Destination Location	A string. For example: DADDRESS=500 Oracle Parkway
DADDRESS2	No	Address Second Line of Destination Location	A string. For example: DADDRESS2=Redwood City, CA
DADDRESSLL	No	Address Last Line of Destination Location	A string. For example: DADDRESSLL=US
DBLOCK	No	Block of Destination Location	A string. For example: DBLOCK=Block 400
DCITY	No	City of Destination Location	A string. For example: DCITY=Redwood City
DCOUNTY	No	County of Destination Location	A string. For example: DCOUNTY=San Mateo
DSTATE	No	State of Destination Location	A string. For example: DSTATE=CA
DZIP	No	Postal Code of Destination Location	A string. For example: DZIP=94065
DZIPEXT	No	Postal Code Extension of Destination Location	A string. For example: DZIPEXT=5423
DCOUNTRY	No	Country of Destination Location	A string. For example: DCOUNTRY=US
DLAT	No	Latitude of Destination Location	(Double) For example: DLAT=37.2433
DLNG	No	LLongitude of Destination Location	(Double) For example: DLNG=-122.3452
DNAME	No	Name of Destination Location	A string. For example: DNAME=Golden Gate Park

Output Parameters

The Driving Directions Module includes the following output parameters:

Table 20-5 Output Parameter of the Driving Directions Module

Parameter Name	Mandatory	Description	Valid Value
STATUS	No	The status of a mobile call.	(OK) CANCEL (Cancelled)

20.3 The Business Directory Module

The Business Directory module provides user with a complete business directory. This module is built on the Oracle9iAS Wireless Location Application Component API.

This module provides a "yellow pages" type interface to look for the addresses and phone numbers of registered businesses in a given radius. It has search capabilities for business names or categories. Browsing through categories is also enabled. If no location parameters are passed to this module, the location module is invoked to obtain location data for the search.

20.3.1 Configuring the Business Directory Input Parameter

This module requires the Oracle9iAS Wireless business directory provider.

Table 20-6 Requirements for the Business Directory Module

Name	External Provider(s)	Instructions	From
Business Directory Provider	otn.oracle.com	See Section 15.1.3.	2.0

This module does not require scripts.

20.3.1.1 Configuring the Input Parameters

The Business Directory includes the following input parameters:

• ORACLE_SERVICES_LOCATION_BIZDIR_RECS_PER_PAGE
  • Description: Items per page. Used to indicate how many businesses/categories are displayed per page.

  • Default Value: 9

20.3.1.2 Linking to the Business Directory

You link to the Business Directory Module using the following virtual URL:

omp://oracle/services/location/bizdir

The Business Directory Module includes the following input call parameters:

Table 20-7 The Input Call Parameters of the Business Directory Module

Parameter Name	Mandatory	Description	Valid Value
PH	No	Phrase (keywords) to search for.	A string. For example: PH=Pizza PH=Restaurants PH=Oracle
FC	No	Full category of the business. This category is defined in the YP mapping XML file, which is specified using the Oracle9iAS Wireless Webtool.	A string. For example: FC=/Business/Restaurant/Italian For example: FC=/Business/Automotive/Dealer/New/BMW
CN	No	Company Name	A string. For example: CN=Oracle Corp.
FL	No	Address First Line	A string. For example: FL=500 Oracle Parkway
SL	No	Address Second Line	A string. For example: SL=Redwood City, CA
LL	No	Address Last Line	A string. For example: LL=US
BL	No	Block	A string. For example: BL=Block 400
CI	No	City	A string. For example: CI=Redwood City
CT	No	County	A string. For example: CT=San Mateo
ST	No	State	A string. For example: ST=CA
PC	No	Postal Code	A string.For example: PC=94065
PCE	No	Postal Code Extension	A string. For example: PCE=5423
CO	No	Country	A string. For example: CO=US
LT	No	Latitude	(Double) For example: LT=37.2433
LN	No	Longitude	(Double) For example: LN=-122.3452
N	No	Name	A string. For example: N=Golden Gate Park

Output Parameter

The Driving Directions Module includes the following output parameter:

Table 20-8 Output Parameter of the Driving Directions Module

Parameter Name	Mandatory	Description	Valid Value
STATUS	No	The status of a mobile call.	(OK) CANCEL (Cancelled)

20.4 Maps Module

The Maps module provides broad and detailed maps for a given location, supports map tiling and image map transformation for different devices. This module integrates with the Driving Directions module and is built upon the Oracle9iAS Wireless Location Application Component API.

20.4.1 Configuring the Maps Input Parameters

This service requires the Oracle9iAS Wireless mapping provider.

Table 20-9 Requirements for the Maps Module

Name	External Providers	Instructions	From
Mapping Provider	otn.oracle.com	See Section 15.1.3.	2.0

20.4.2 Configuring the Input Parameters

The Maps module includes the following input parameters:

• ORACLE_SERVICES_LOCATION_MAPS_WIDTH_MS
  • Description: The width of maps on PDAs and PC browsers.

  • Default Value: 200

• ORACLE_SERVICES_LOCATION_MAPS_HEIGHT_MS
  • Description: The height of maps on PDAs and PC browsers.

  • Default Value: 200

20.4.3 Linking to the Maps Module

You link to the Maps module using the following virtual URL:

omp://oracle/services/location/maps

Input Call Parameters

The Maps module includes the following input call parameters:

Table 20-10 Input Call Parameters of the Maps Module

Parameter Name	Mandatory	Description	Valid Value
CN	No	Company Name	A string. For example: CN=Oracle Corp.
FL	No	Address First Line	A string. For example: FL=500 Oracle Parkway
SL	No	Address Second Line	A string. For example: SL=Redwood City, CA
LL	No	Address Last Line	A string. For example: LL=US
BL	No	Block	A string. For example: BL=Block 400
CI	No	City	A string. For example: CI=Redwood City
CT	No	County	A string. For example: CT=San Mateo
ST	No	State	A string. For example: ST=CA
PC	No		Postal Code A string. For example: PC=94065
PCE	No	Postal Code Extension	A string. For example: PCE=5423
CO	No	Country	A string. For example: CO=US
LT	No	Latitude	Double. For example: LT=37.2433
LN	No	Longitude	Double. For example: LN=-122.3452
N	No	Name	A string. For example: N=Golden Gate Park
LMN	No	Location Mark Name	A string. For e xample: LMN=Office
STATUS	No	The status of the module call.	(Ok) CANCEL (Cancelled)

Output Parameter of the Maps Module

The Maps module includes the following output parameter

Table 20-11 Output Parameter of the Map Module

Parameter Name	Mandatory	Description	Valid Value
STATUS	No	The status of a mobile call.	(OK) CANCEL (Cancelled)

20.5 Extending the Mobile Modules

The location modules use the Oracle9iAS Wireless Location Application Component APIs. These Java APIs can be used independently to write other Location Based Services (LBS). For more information on the Location Application Component API, see Section 15.2.

This section describes the main classes of these APIs. For each class, the typical use cases and the code example for each use case are given.

20.5.1 The oracle.panama.model.LocationMark class

This interface represents a Location Mark saved by the user. It extends the Location interface which represents a location.

The typical operations a user wants to perform include:

1. Get all Location Marks of a user

   LocationMark[ ] locationmarks = iasUser.getLocationMarks();  
   

   where iasUser is an object of User, which represents a user of Oracle9iAS Wireless wireless.

2. Get and set attribute(s) of a Location Mark The LocationMark class has specific "get" and "set" methods. For example, to get the city of a Location Mark, use String city = locationmark.getCity();

   To set the city, use

   locationmark.setCity(city);

   For a complete listing of these methods, refer to the Oracle9iAS Wireless javadoc.

3. Create a Location Mark

   String locationmark_name = "Office";
   LocationMark lm = 
   MetaLocator.getInstance().getModelFactory().createLocationMark(locationmark_
   name,iasUser);
   Location l = SpatialManager.createLocation("Oracle", "500 Oracle 
   Parkway","", "Redwood City, CA 94065", "US");
   lm.setLocation(l);
   Locator.getInstance().getPersistentLocator().getSessionManager().commitSessi
   on();  
   

4. Delete a Location Mark

   LocationMark lm = 
   MetaLocator.getInstance().getModelServices().lookupLocationMark(locationmark
   _id);
   lm.delete();
   MetaLocator.getInstance().getModelFactory().save(); 
   

where locationmark_id is an automatically generated unique Java "long" which identifies the Location Mark. To get this id, call getId() on the LocationMark object.

5. Update a Location Mark The steps to update a Location Mark is similar to creating a new one. First, get the Location Mark object. Second, update the location. Finally, commit the changes.

   LocationMark lm = 
   MetaLocator.getInstance().getModelServices().lookupLocationMark(locationmark
   _id);   
   lm.setCity("San Francisco");
   Locator.getInstance().getPersistentLocator().getSessionManager().commitSessi
   on();    
   

6. Set a Location Mark as the default location

   LocationMark lm = 
   MetaLocator.getInstance().getModelServices().lookupLocationMark(locationmark
   _id);
   iasUser.setDefaultLocationMark(lm);
   MetaLocator.getInstance().getModelFactory().save(); 
   

20.5.2 The oracle.panama.spatial.geocoder.Geocoder class

The Geocoder interface abstracts the implementation of a geocoder. The geocoder implementation is specific to the geocoding content provider. For example, to use the geocoding content from MapQuest, the implementation class is oracle.panama.spatial.core.geocoder.GeocoderImplMapQuest, which is supplied with Oracle9iAS Wireless. At the module level, the specific implementation class is transparent.

The typical operations a user wants to perform include:

1. Get an instance of Geocoder

   Geocoder geocoder = SpatialManager.getGeocoder();
   
   

2. Geocode a location. There are two ways:
   • Use the Geocoder interface:
     

     Location[} locations = geocoder.geocodeAddress(location, matchmode); 
     

     Where location is a Location object and matchmode is a String indicating how the geocoder should try to geocode the location. The valid values for matchmode are:

     • MATCH_MODE_NORMAL, MATCH_MODE_STANDARD, MATCH_MODE_TIGHT

     • MATCH_MODE_RELAXED

     Refer to the Oracle9iAS Wireless javadoc for details.

   • Use the Location interface to geocode a location.

     location.geocode(checkWhetherNecessary, makeCorrections);

     where checkWhetherNecessary and makeCorrections are two booleans.

20.5.3 The oracle.panama.module.location.LocationHistoryManager class

The LocationHistoryManager class manages the locations saved automatically by other modules or applications. It has methods for:

1. Get all automatically saved locations (that is, location history).

   Location[] locations = LocationHistoryManager.getLocations(iasUser);
   

This method returns an array of locations sorted by their last used time stamps.

2. Update the location history with a location.

   The location history is a stack of locations saved by modules or applications. The history can be used by modules and applications to eliminate the need for users to enter those locations again. The history also can be shared among all location based services. For example, a restaurant found using the Business Directory module is saved in the history and is be automatically available when the user uses the Driving Directions module to get directions to that restaurant. The maximum size of the stack is configurable by the ORACLE_SERVICES_LOCATION_PICKER_STACKSIZE service parameter. When the stack size is below the maximum, new locations are added to the stack. When the stack size reaches the maximum, a new location replaces the earliest location on the stack (that is, the location with the earliest time stamp).

   long id =LocationHistoryManager.updateHistory(l, iasUser);

   Where l is an object of LocationHelper, a class that implements the Location interface. The above code updates the location history stack with location "l" for iasUser. Refer to Oracle9iAS Wireless modules javadoc for details on the LocationHelper class.

20.5.4 The oracle.panama.spatial.router.Router class

The Router interface abstracts the implementation of a router, which provides turn-by-turn driving directions. The router implementation is specific to the routing content provider. For example, to use the routing content from MapQuest, the implementation class will be oracle.panama.spatial.core.router.RouterImplMapQuest, which is supplied with Oracle9iAS Wireless. At the module level, the specific implementation class used is transparent. The typical operations a user wants to perform include:

1. Get an instance of Router.

   Router router = SpatialManager.getRouter();
   

2. Get Driving Directions between two locations.

   RoutingResult rr = router.computeRoute(starting_location,    destination_
   location, via_points, settings, locale);
   
   

   where starting_location and destination_location are two Location objects, via_points is an array of Location objects that represent the desired via points along a route (null is okay if no via points is needed), settings is a RoutingSettings object that indicates the routing options (see below for details), and locale is the desired locale for directions output (for example, mile is used as distance unit for United States, whereas km is used in Canada). Once the RoutingResult object is obtained, you can iterate through the maneuvers to get turn-by-turn directions. For example:

   for (int i = 0; i < rr.getManeuvers().length; i++){
     Maneuver m = rr.getManeuvers()[i];
     System.out.println(m.getNarrative());
   } 
   

3. Set Driving Directions options Use RoutingSettings class to set options. For example, to get the overview map of a route:

   RoutingSettings settings = new RoutingSettings();
   settings.setRequestMap(true);    
   settings.setSecondaryOption(RoutingOption.overviewMapWidth, MAP_WIDTH+""); 
   settings.setSecondaryOption(RoutingOption.overviewMapHeight, MAP_HEIGHT+""); 
   RoutingResult rr = router.computeRoute(starting_location, destination_
   location, via_points, settings, locale); 
   String url = rr.getOverviewMapURL(); 
   
   

Refer to Oracle9iAS Wireless javadoc for details of available options.

20.5.5 The oracle.panama.spatial.mapper.Mapper class

The Mapper interface abstracts the implementation of a mapper, which provides maps. The mapper implementation is specific to the mapping content provider. For example, to use the mapping content from MapQuest, the implementation class will be oracle.panama.spatial.core.mapper.MapperImplMapQuest, which is supplied with Oracle9iAS Wireless. At the module level, the specific implementation class used is transparent. The typical operations a user wants to perform include:

1. Get an instance of Mapper.

   Mapper mapper = SpatialManager.getMapper();
   

2. Get the map of a location There are several methods available in the Mapper class. For example:

   String mapurl = mapper.getMapURL(location, ImageFormats.GIF,    
     location.getLongitude() - zoomlevel * MAP_LNG_SIZE, 
     location.getLongitude() + zoomlevel * MAP_LNG_SIZE, 
     location.getLatitude() - zoomlevel * MAP_LAT_SIZE,    
     location.getLatitude() + zoomlevel * MAP_LAT_SIZE, 
     MAP_WIDTH, MAP_HEIGHT, 
     false);
   
   

Refer to the Oracle9iAS Wireless javadoc for details of this and other mapping methods.

20.5.5.1 The oracle.panama.spatial.yp.YPFinder class

The YPFinder interface abstracts the implementation of a "YP" like business directory service. The YPFinder implementation is specific to the business directory content provider. For example, to use the content from MapQuest, the implementation class will be oracle.panama.spatial.core.yp.YPFinderImplMapquest, which is supplied with Oracle9iAS Wireless. At the module level, the specific implementation class used is transparent. The typical operations a user wants to perform include:

1. Get an instance of YPFinder.

   YPFinder finder = SpatialManager.getYPFinder();
   

2. Get business categories The YPFinder class supports the "browsing" of business categories. These categories are defined by user based on the content provider in oracle.panama.spatial.yp.YPCategories.xml file. The location of this file needs to be specified in Oracle9iAS Wireless webtool. At runtime, the YPFinder class has methods that support the browsing of the category hierarchy. For example, to start at the root category,

   YPCategory root = finder.getCategoryAtRoot();

   Then to get the subcategories at root,

   YPCategory[] cats = root.getSubCategories();

3. Search for businesses. The "search" operation can be performed with two classes: YPFinder and YPCategory. The search can be proximity search (that is, around a location within a certain radius), using such criteria as searching a city, or a zipcode.

   
   YPBusiness[] bizes = root.getBusinessesInRadius(location, raidus_in_meters, 
   locale); 
   YPBusiness[] bizes = finder.getBusinessesInSameCity(bizname, location, 
   locale);  
   YPBusiness represents a business and extends the Location class. So you can 
   get the address of the business using this class or use getTelephone() to 
   get the business phone. 
   
   

20.5.5.2 Location Mark API Examples

This example creates a Location Mark, "Office". Note that the call SpatialManager.createLocation() automatically geocodes the location.

Source

import oracle.panama.model.LocationMark;
import oracle.panama.model.Location;
import oracle.panama.model.MetaLocator;
import oracle.panama.core.util.Locator;
import oracle.panama.spatial.SpatialManager;
String locationmark_name = "Office";
LocationMark lm = 
MetaLocator.getInstance().getModelFactory().createLocationMark(locationmark_
name,iasUser);     
Location l = SpatialManager.createLocation("Oracle","500 Oracle Parkway","", 
"Redwood City, CA 94065","US");
lm.setLocation(l);
Locator.getInstance().getPersistentLocator().getSessionManager().commitSession()
;      

20.5.5.3 Driving Directions API Examples

This section provides an example of the Driving Directions API and its output.

Source

import oracle.panama.model.LocationMark;
import oracle.panama.model.Location;
import oracle.panama.spatial.SpatialManager;
import oracle.panama.spatial.router.Router;
import oracle.panama.spatial.router.RoutingSettings;
import oracle.panama.spatial.router.RoutingOption;
import oracle.panama.spatial.router.RoutingResult;
import oracle.panama.spatial.router.Maneuver;
Location starting= SpatialManager.createLocation("Oracle","500 Oracle 
Parkway","", "Redwood City, CA 94065","US");
Location destination = SpatialManager.createLocation("Autobahn Motors","700 
Island Pkwy","", "Belmont, CA","US");
Router r = SpatialManager.getRouter();
RoutingSettings settings = new RoutingSettings();         
settings.setRequestMap(true);
settings.setSecondaryOption(RoutingOption.overviewMapWidth, "400");
settings.setSecondaryOption(RoutingOption.overviewMapHeight, "400");
RoutingResult rr = r.computeRoute(starting, destination, null, settings, 
Locale.getDefault())
for (int i = 0; i < rr.getManeuvers().length; i++){
  Maneuver m = rr.getManeuvers()[i];
  System.out.println((i+1)+")"+m.getNarrative());
} 

Output

1. Begin at 500 Oracle Pkwy on Oracle Pkwy and go West for 0.6 miles (0.6Miles)

2. Bear right on Island Pkwy and go West for 0.3 miles (0.3Miles)

3. Make U-turn on Island Pkwy and go South for 80 feet to Island Pkwy (0.0Miles)

20.5.5.4 Maps API Examples

Source

import oracle.panama.model.LocationMark;
import oracle.panama.model.Location;
import oracle.panama.spatial.SpatialManager;
import oracle.panama.spatial.mapper.Mapper;
import oracle.panama.imagex.ImageFormats;
Location location= SpatialManager.createLocation("Oracle","500 Oracle 
Parkway","", "Redwood City, CA 94065","US");

Mapper mapper = SpatialManager.getMapper();
String mapurl = mapper.getMapURL(location,      
  ImageFormats.GIF, 
  location.getLongitude() - 0.008, 
  location.getLongitude() + 0.008, 
  location.getLatitude() - 0.008, 
  location.getLatitude() + 0.008, 
  400,      
  400, 
  false);

20.5.5.5 YPFinder API Examples

This example searches for Pizza Hut within two miles of Oracle

Source

import oracle.panama.model.LocationMark;
import oracle.panama.model.Location;
import oracle.panama.spatial.SpatialManager;
import oracle.panama.yp.YPFinder;
import oracle.panama.yp.YPBusiness;
Location location= SpatialManager.createLocation("Oracle","500 Oracle 
Parkway","", "Redwood City, CA 94065","US");
YPFinder yp = SpatialManager.getYPFinder();
YPBusiness[] bizes = yp.getBusinessesInRadius("pizza hut", location, 2*1609.344, 
null);
for (int k = 0; k < bizes.length; k++) {
  YPBusiness biz = (YPBusiness) bizes[k];
  double dist = biz.getDistance(location);
  bizname = biz.getCompanyName();
  bizaddr = biz.getAddressLine1();
  bizcity = biz.getCity();
  bizstate = biz.getState();
  bizcountry = biz.getCountry();
  bizphone = biz.getTelephone();
  // output results
  //...

}