Compass direction - azimuth

Does anyone know if Oracle has a function to calculate the azimuth (compass direction) between 2 geodetric points. I see that SDO_GEOM.SDO_DISTANCE will return the distance, so I would assume there is also a way to determine the direction.
In order to calculate azimuth manually, I would need to calculate the distance manually as well. That seems to defeat the pupose of using spatial.
Any ideas?

Hi,
This functionality is not currently in Spatial. There is hope it will be available in a soon-to-be-released version.

Similar Messages

Feature Request: 7d Mark II - Add option to show compass direction in viewfinder.

Please add option to show compass direction in the viewfinder display.

Skirball wrote:
That's interesting, I didn't know that they added new information to the viewfinder. I agree, it's a nice addition. That said, I'll still say that any change is unlikely for three reasons:
1) I'm guessing that the overlay is still some sort of LCD type technology, where you can't simply program in new information at will.
2) Even if I'm wrong and it is a customizable display, unless Canon programmed it with the intent of adding variables later it's probably more work than you think to add in a new feature and fully validate the design change.
3) Historically Canon has been very reserved with firmware updates. Usually they're just to fix errors, not add features. The one exception to that are updates to the 1Dx, which Canon seems happy to do. As they should, for a $6700 camera. But plenty of changes (such as the auto-ISO exposure compensation) could easily trickle down to other models. Not to mention allowing reprogramming of rear panel buttons for things like AF mode toggle, or white balance (6D). And they released the 7D2 with the same GPS battery drain issue they seem to refuse to acknowledge. Sorry, I think the chance of putting a compass in the viewfinder is slim. Just my opinion.
Your first 2½ points are valid, along with one you didn't make: Incorporating a compass into the viewfinder introduces a magnetic field in a location where you probably don't want one.
I think your third point is a bit overstated, however. The 7D (and I think also the 5D3) has had a fairly major firmware update during its lifetime that did include an additional feature that I thought was importatnt: the ability to name image files before they leave the camera. Since I have two 7Ds, it's very helpful to be able to see quickly which pictures were taken with which camera. And when I share photo shoots with my wife, it helps me tell my pictures from hers. (She uses a Rebel, which lacks the in-camera naming feature.)
All that aside, the value of an in-camera compass is at best debatable. If you actually need it, you probably want it to be accurate; and unless you never leave your home town, you'd have to recalibrate it often to keep it in sync with true north (or south). I think I'd consider it just another unnecessary distraction.
Bob
Boston, Massachusetts USA

Compass direction in Extended Info

I have the new new Sony Cybershot HX5V which records GPS co-ordinates, altitude and compass setting with each photo.
In iPhoto 09 I pull up extended info for a photo and see the GPS coordinates and the Altitude but I do not see any Compass setting data i.e. which direction the camera was facing when the photo was taken.
Does iPhoto not extract this data off the camera or do I need to change a setting in iPhoto?
Cheers!

These are no GPS options in iPhoto - you can suggest to Apple - iPhoto Menu ==> provide iPhoto feedback
You might try EXIF viewer - http://homepage.mac.com/aozer/EV/ - and see what fields are there and their values
LN

IPhone 6, 6 photo direction 180 deg error

I have an iPhone 6+ and my wife has an iPhone 6. On both phones, when using the built in camera app, the direction of the photo as reported in the metadata is 180 deg off. For example, if I take a photo in the facing North the metadata is decoded as South by Lightroom. A photo taken facing West is reported as East by Lightroom. This error is present in both landscape and portrait orientation.
If I take a photo with my old iPhone 5S (currently used as an iPod) the compass direction as reported in Lightroom is correct.
Anyone else seeing this problem?

Update....It appears the problem started with iOS 8. My images taken on my iPhone 5s after installing iOS 8 are also 180 deg out. Those taken with iOS 7x are correct.
I have reported this via feedback for the iPhone.

Maps in E72, compass and map rotation glitches

The new OviMaps 3.03 and E72 with the magnetic compass has a few problems:
- The compass "takes over" map rotation in E72, the map will not rotate according to GPS heading information at all. If the compass does not work (magnet nearby, inside a car etc.), the map will not rotate automatically, it's relying solely on the compass. Very annoying, especially since the compass loses its calibration quite easily. Thus, the map is unsuable in a car or a "spora" (tram).
- When using an external bluetooth GPS, the compass is "whited out", apparently being overridden by the heading data from the GPS. ...which is not shown, the compass wheel simply turns white. This happens as long as a BT GPS is used and is giving speed and heading to the E72. This is a clear bug. Nokia, please solve this.
- There is apparently no way to get the E72 OviMaps 3.03 to rotate according to GPS heading info?
- The tendency to lock the position to a nearby road is much too strong in 3.03. This is very bad, since the map rotation is affected by the orientation of the road onto which the dot is placed, further hampering the direction of map rotation. Since most people will use the OviMaps while walking, this "road locking" tendency needs to be tuned down a lot. It makes the compass &rotation ever less usable.
- The "simplified" user interface of OviMaps is now giving even less GPS information than before. Next it will probably be as useless a an iPhone, when it comes to wanting to know how many satellites it is trying to get a fix on. Believe it or not, this is very useful information to anyone who wants to get a fix in a challenging environment. It's frustrating to watch a single yellow line blinking an not having a clue wheter one is missing one or four satellitse fixes to get a location.
Has anyone else been having these same problems, especially with the rotation? (E72-1 022.007, OviMaps 3.03)
I've played with a huge bunch of different GPS & Mapping devices ever since the NAVSTAR system went public some 20 years ago. It is fun to see how the system is now quickly becoming a household thing in every single pocket, but to keep it genuinely helpful you need to be extra careful with these little features and tunings.
(BTW; I've never gotten the compass to calibrate with the 8-move instructed in the manual. 4 or 5 quick flicks of the wrist are the only way to get the thing calibrated at all)
In many other ways, the OviMaps is a nice and handy application. Thanks.
/tutka

Hi my fE 72 firmware ver is 024.029, upgraded to 3.03 maps two days back. There are issues and Nokia better not sleep on them other wise this is useless for the users.
The problems in previous and this ver -
- the compass does not lock easily, will remain in yellow or red, do what everr u do?
- As pointed out in by you, in side car or near any electric applices , the compass direction goes heywire.
- sycronisation gets stuck
TYhe new version -
- In old version there was option in the setting to turn the compass on or off , so while driving if the compass is not getting locked, u could turn it off and by default the map would orient itself in the driving direction. now as pointed out by you. the the map compass doesnt get locked or the calibration doesnt stay at speed and the map gets locked with north to top, so there are situation when your poisition in the maps is moving in diametrically opposite/ tangential direction to your travel .
How can a compasny bungle up on such safety and reliability issues, specially on a product ( navigation/maps)which is in existance for almost a DECADE AND IS ABSOLUTELY MATURE PRODUCT TECHNOLOGY WISE.
tHE e72 SOFTWARE WAS DEVELOPED IN SLUMBER SO IS THIS 3.03 MAPS. nOKIA GET OUT OF HYBERNATION, THERE ARE TOO MAY ALTERNATIVES FOR CUSTOMERS NOW.
Nokia either take off this from shelf or be ready to get public lawsuits on accout of accidents caused by people driving with these maps on.

Gen2 Ipod Touch ios 4.2 compass available?

Is there a compass for the Gen2 Ipod Touch, iOS 4.2?
One with a magnetic declination adjustment, preferably?

ps, need not be magnetic, a sun compass application would work fine for me, if the ipod doesn't do magnetic compass direction -- havent' found one yet

Is this type of query possible (select with rows stopping based on match)

I'm trying to write a SQL query and suspect it can't be done. Or at least, I can't mentally grasp it, despite various stabs with subqueries. I've simplified it by changing the metaphor here a little.
Let's say I have a truck in some city (say, Chicago). There are various roads leading out of that city, with routes we'll label according to compass points (N, NE, SW, etc.) Each truck can carry only one shipment. It starts going along its road, and as soon as it comes to a city that needs its shipment, it stops.
Yes, a cooked example, but it's similar to my problem.
Here is a table:
TABLE: truck_routes
scenario (integer - different possible scenarios)
route (NE, SW, etc. - 8 compass directions)
destination (cities along that road)
sequence_number (order in which to go to those cities)
So if I have a trucks in Chicago, I can say
SELECT route, sequence_number, destination
FROM truck_routes
WHERE scenario = 10 (or whatever)
ORDER BY road_out, sequence_number;
And I'd get a report like this:
SE 1 Gary
SE 2 Valparaiso
SE 3 Plymouth
SE 4 Warsaw
NE 1 Michigan City
NE 2 Kalamazoo
NE 3 Grand Rapids
NE 4 Cadillac
NE 5 Traverse City
So far so good. I have another table with a list of cities that need to receive the shipment:
TABLE: cities
scenario (integer - different possible scenarios)
route (NE, SW, etc. - 8 compass directions)
destination (same keys as in truck_routes)
e.g.:
10 SE Valparaiso
10 SE Warsaw
10 NE Cadillac
10 NE Traverse City
Now...the tricky part...how do I rewrite the query above so that after a truck hits a city that needs a shipment (in that scenario) it stops? In other words, I want a report (for all routes) of what cities the truck will stop at - and as mentioned, it stops at the first one it makes a delivery. I don't want to see rows beyond that. So the report would look like this:
SE 1 Gary
SE 2 Valparaiso
NE 1 Michigan City
NE 2 Kalamazoo
NE 3 Grand Rapids
NE 4 Cadillac
Gary shows up because it doesn't require a delivery. Valparaiso (SE route, sequence_number 2) shows up because it takes the delivery. The rest of the Southeast route doesn't show up. Same thing for the NE route.
There are scenarios where I'd actually want to stop at the city just prior to the delivery destination, etc., and of course in the real world it's more complicated, but I think if I could get this model working I could flesh it out into a real-world query.
I can certainly code something in PL/SQL to do this, or do it in application logic - but I'm wondering if there is a way to do it in a single SQL statement? I suspect there's something that could be built with subqueries and sorting, but...I can't quite reach it ;-)

WITH report AS(
    SELECT 'SE' route, '1' seq_num, 'Gary' dest FROM DUAL UNION ALL
    SELECT 'SE' route, '2' seq_num, 'Valparaiso' dest FROM DUAL UNION ALL
    SELECT 'SE' route, '3' seq_num, 'Plymouth' dest FROM DUAL UNION ALL
    SELECT 'SE' route, '4' seq_num, 'Warsaw' dest FROM DUAL UNION ALL
    SELECT 'NE' route, '1' seq_num, 'Michigan City' dest FROM DUAL UNION ALL
    SELECT 'NE' route, '2' seq_num, 'Kalamazoo' dest FROM DUAL UNION ALL
    SELECT 'NE' route, '3' seq_num, 'Grand Rapids' dest FROM DUAL UNION ALL
    SELECT 'NE' route, '4' seq_num, 'Cadillac' dest FROM DUAL UNION ALL
    SELECT 'NE' route, '5' seq_num, 'Traverse City' dest FROM DUAL
cities AS (
    SELECT '10' scenario, 'SE' route, 'Valparaiso' city FROM DUAL UNION ALL
    SELECT '10' scenario, 'SE' route, 'Warsaw' city FROM DUAL UNION ALL
    SELECT '10' scenario, 'NE' route, 'Cadillac' city FROM DUAL UNION ALL
    SELECT '10' scenario, 'NE' route, 'Traverse City' city FROM DUAL
need_a_shipment AS (
      SELECT r.*
          , CASE WHEN EXISTS( SELECT 'Y' FROM cities c WHERE c.route = r.route AND c.city = r.dest )
                 THEN 'Y'
                 ELSE 'N'
            END need_a_shipment
    FROM report r
SELECT route
      , seq_num
      , dest
      , need_a_shipment
FROM need_a_shipment n
WHERE seq_num <= ( SELECT MIN(seq_num) FROM need_a_shipment
                    WHERE route = n.route AND need_a_shipment = 'Y' )
ORDER BY route DESC, seq_num
ROUTE SEQ_NUM DEST          NEED_A_SHIPMENT
SE    1       Gary          N
SE    2       Valparaiso    Y
NE    1       Michigan City N
NE    2       Kalamazoo     N
NE    3       Grand Rapids N
NE    4       Cadillac      Y

Identify type of ipod

Guys, I have been given an old ipod with no manuals or paperwork. I'm trying to buy a car cigarette lighter charger for it and thought they would be compatable.
I have just one which didn't work on mine but works on a modern ipod.
So I need to work out what model I have.
I believe its about 6 or 7 years old, maybe more.
I think its a third generation which causes the problem because I get sent stuff for a modern 3rd generation.
Its about 100mm x 70mm white. It has the click wheel with four buttons above.
It has a 20gb drive.
I can find two serial numbers, one on the back U23430JDPNT, and one in the software model M9244B.
Please can someone identify mine and tell me where I can get a working charger.
Thanks Bob.

You seem to be confusing terms.
I think its a third generation which causes the problem because I get sent stuff for a modern 3rd generation.
There is no "modern" 3rd gen full-size iPod, although there is a recent 3rd gen iPod nano (current version of the iPod nano is 4th gen).
Its about 100mm x 70mm white. It has the click wheel with four buttons above.
A "click wheel" is the one that clicks down at the four compass directions (which is why it is called a click wheel). If the wheel is touch sensitive but does not click down and there are four round touch buttons between the wheel and screen, you have a 3rd gen iPod, aka +iPod (Dock Connector)+.
Your charging issue with the 3rd gen iPod is because it was designed to be used with FireWire. It only charges if you connect it with a FireWre docking cable. I believe this is because the voltage between FireWire and USB charging is different (and all current iPods use USB charging). Therefore, you would have to find an old product that was sold back when these iPods and the 4th gen were being sold as new.
Do you have the square white FireWire power adapter that came with those iPods? If you do, or can get one (along with a FireWire docking cable), you can get one of those car lighter adapters that let you plug in regular two-prong power cords. Then just plug in the standard FireWire power adapter.

Colorchecker passport and the DNG profile editor

I finally got around to getting a Colorchecker passport to use with the DNG profile editor.
I was secretly hoping I could save time by shooting the chart on location and make an instant profile out of that - then the colors would be at least "close ballpark" so I would just have to apply white balance and then move on to more specific adjustments. But of course it wasn't that easy, it still takes a fair bit of color tweaking to get right in most circumstances.
So I'm wondering if my energy would be better spent trying to perfect one good dual illuminant general profile. For this I would use 3000 K tungsten at one end and 5500 K studio flash at the other. Or would it be better to use overcast daylight? In either case it's obviously important to ensure the chart is absolutely evenly lit.
And then I should probably have a separate profile for fluorescent tubes.
I'm curious what other people's experiences with the colorchecker/DNG profile editor are? How are you using it?

The color profile changes with the lighting, so a profile that was computed for daylight won’t be right for tungsten or fluorescent. Keep in mind that a custom camera profile is the set of corrections on top of an existing Adobe profile that the DNG has assigned to it, perhaps Adobe Standard, and all Adobe profiles are dual-illuminant profiles, so it makes sense you’d want to also create a dual-illuminant profile for general purpose use that has the same two lighting scenarios as Adobe used: 2850K and 6500K. The 6500K is the tricky one because full sun is warmer, closer to 5000K, and you need the right amount of haze to create 6500K sunlight, unless you are using standard D65 bulbs, indoors, which is likely what Adobe does.
I use a dual-illuminant profile for general purpose use, but since the WB-Tint values of both the tungsten and daylight ends are close to zero, lighting that has a tint not close to zero needs a separate profile. The common example is the greenish light from fluorescents, and I have several single-illuminant profiles for various artificial lighting scenarios with WB-Tint values that are relatively non-zero. I also have ones for very red sunsets and very blue twilight. If I had studio lighting I’d make a profile for that. Sometimes I make a custom profile for a church or other venue that has significant non-neutral walls or ceilings, or where sunlight through the stained-glass windows shining on the walls are giving a significant color-cast including a non-zero tint value to the lighting. If you know you’ll be doing some shots near a large amount of tall, green vegetation then a custom color profile can correct for the green tinge to the ambient lighting coming down from above mixing in with the sunlight.
Adding to the suggestion about wearing neutral clothing, I’d argue for dark neutral clothing because something lighter clothing will reflect environmental colors (sunlit vegetation or brick walls, etc, outdoors) and not be neutral.
Besides non-neutral clothing, try to avoid areas that have green grass or tree leaves or brick buildings that also color the light and reflect off the colorchecker. For the sunlit shots, I put my colorchecker face up on the sidewalk or parking lot, to avoid coloration from the grass and far away from trees or buildings especially in the direction I’m pointing the camera, so the only lighting is direct sun and ambient blue-sky, possibly diffused by hazy clouds. I point the camera down at the colorchecker, at a 45-degree angle and at a compass direction and not directly toward the sun, nor directly away from the sun. I try to shoot the target that is face up on the ground perhaps at a 90-degree angle from the sun to minimize any residual glare from the colorchecker’s slightly non-matte surface. Obviously directly away from the sun, the color-checker will have my shadow on it or I will be blocking the light from the sky near the sun.
I use the same sort of process for the tungsten end, choosing a room with neutral walls and put the target relatively flat on the floor facing up, perhaps tipped up somewhat toward the light, but not so much as to have any glare from the lighting, either, in other words, not with the lighting directly behind the camera, but somewhat over to the side.

Incorrect Locations

When I download photos contain GPS co-ordinates (from a Lumix DMC-TZ10), iPhoto sometimes assigns the wrong location. It seems to have a preferred "default" location which it has picked up from earlier photos and uses this in preference to the real one. When I delete the incorrect location name on the photo, the place name reverts to "no name", but the location is shown correctly on the map.
Any suggestions as to what's going wrong and how I deal with it?
As a subsidiary comment, my Lumix seems to be able to generate much more specific place names than iPhoto can, but this data is lost when I download the photos. I've read that this data can't be transferred, but if anyone knows otherwise, please let me know.
Many thanks.

When I download photos contain GPS co-ordinates (from a Lumix DMC-TZ10), iPhoto sometimes assigns the wrong location. It seems to have a preferred "default" location which it has picked up from earlier photos and uses this in preference to the real one. When I delete the incorrect location name on the photo, the place name reverts to "no name", but the location is shown correctly on the map.
Any suggestions as to what's going wrong and how I deal with it?
I do not understand what you are seeing. Are you saying that the coordinates are correct but iPhoto uses a different place name (I have never seen or herd of this except where there are database errors) or that the coordinates are of an older photo (My Sony will do this if I do not have GPS sync in the new location)
As a subsidiary comment, my Lumix seems to be able to generate much more specific place names than iPhoto can, but this data is lost when I download the photos. I've read that this data can't be transferred, but if anyone knows otherwise, please let me know.
As you were told you can not currently use the location name data from the camera (or the compass direction if the camera includes that) - suggest to Apple - iPhoto menu ==> provide iPhoto feedback
LN

Ipod troubles (again)

I'm running windows XP, I have 2 ipods a 160gb Ipod classic and also an old 40gb ipod. I have just bought myself an external hard drive to store all my music on.
I was aiming to have all one genre on the 160gb ipod and all another genre on the 40gb ipod.
After a few minor problems i have the external hard drive and the 160gb ipod running together on the same pc (after changing the drive letter on the ipod)
My problem is with the older ipod. Everytime i connect it to my pc my pc freezes and i am unable to do anything until i have unplugged the usb cable, once i have unplugged everything i was trying to open (eg My Computer, itunes) opens straight away.
I had a problem with my old ipod a while ago when i lost all music (however the data still showed up on the "about ipod" on the ipod, just not on itunes or the artists, songs albums on the ipod). Still I hoped to get a reply on this forum (never got a solved answer) So i carried on adding music without a factory reset, hoping i would recover the songs.
The old ipod seemed to be working fine until yesterday when i connected to my pc for the first time in a while.
Now i had burned all my cds again to put on my new ipod i'm not bothered about restarting the old ipod, i would just like to get it to the factory settings again but i'm unsure how, with my pc freezing everytime i put it in.
Please don't tell me "its an old ipod, maybe time for a new one" Thats not what i want to hear. I paid £300+ for it!
Message was edited by: Carlo Baggio

Faulty drive inside the iPod. The 40GB iPods have the thicker two-platter drives inside. The thicker drives seem a bit more delicate, based on my experience, compared to the thinner single platter drives. But any iPod with a hard drive inside is likely to fail at some point because the hard drive becomes worn out or damaged, just as any hard drive is likely to fail at some point for the same reasons.
Does the iPod work normally when it is not connected to the computer? That is, does the screen menu display and work properly, and if it has songs on it, does it play the songs properly?
I'm prety sure its the click wheel.
If the wheel clicks down at the four +compass directions+, it is a clickwheel, and it is a 4th gen. Note: If it's the older touchwheel iPod (with four separate touch buttons), it is a 3rd gen, and it will not work reliably using a USB connection. Those iPods are designed to work with FireWire.
If it is possible to connect the iPod and not have the computer freeze up, I would try using Windows to reformat the iPod (from a My Computer or Windows Explorer) window. Use a full format instead of any option for a quick format. If that completes successfully, run iTunes and use Restore to install and initialize the iPod's software.
If you cannot connect it to the computer without the computer freezing up (and the other iPod works fine with the exact same connection), there's not much more you can try other than opening the iPod and swapping out parts until you find the one that is faulty (most likely the hard drive).

Metadata field exif:GPSImgDirection

I'm using images with the compass direction embedded in the metadata in the exif:GPSImgDirection field. An image opened in Photoshop CS6 shows the value in File | File Info, but when the same image is opened in Lightroom 4.2 this direction information is not displayed even though GPS and Altitude data are displayed. Is there a way of forcing Lr to display this particular field?

You may wish to add your vote here. http://feedback.photoshop.com/photoshop_family/topics/add_image_direction_in_map_module

Help needed regarding CLLocation Manager

Hello everybody,
i am developing a GPS application in which i needs to track the speed of the device/iphone ,i am using the CLCorelocation API's Locate me referral code provided by Apple my problem is that the LocationManager does not updates the current latitude and longitudes thus i am unable to calculate the distance as well as the speed of the device/iphone.
Any kinds of suggestions/code will be highly appreciated please suggest me if i can do something with the Mapkit framework introduced in the sdk 3.0.
thanks in advance

Thanks for your reply i am copying my code what i have implemented and it does not works please have a look at it and let me know what i am doing wrong i will be very helpful to you.
- (void)locationManager:(CLLocationManager *)manager
didUpdateToLocation:(CLLocation *)newLocation
fromLocation:(CLLocation *)oldLocation
ASafeDriverAppDelegate *appDel1 = (ASafeDriverAppDelegate *)[[UIApplication sharedApplication] delegate];
chklat = newLocation.coordinate.latitude;
chklon = newLocation.coordinate.longitude;
appDel1.maxSpeed=0;
double timeDiff;
NSMutableString *update = [[[NSMutableString alloc] init]autorelease];
// Horizontal coordinates
if (signbit(newLocation.horizontalAccuracy)) {
// Negative accuracy means an invalid or unavailable measurement
[update appendString:LocStr(@"LatLongUnavailable")];
} else {
// CoreLocation returns positive for North & East, negative for South & West
[update appendFormat:LocStr(@"LatLongFormat"), // This format takes 4 args: 2 pairs of the form coordinate + compass direction
fabs(newLocation.coordinate.latitude), signbit(newLocation.coordinate.latitude) ? LocStr(@"South") : LocStr(@"North"),
fabs(newLocation.coordinate.longitude),signbit(newLocation.coordinate.longitude ) ? LocStr(@"West") : LocStr(@"East")];
[update appendString:@"\n"];
[update appendFormat:LocStr(@"MeterAccuracyFormat"), newLocation.horizontalAccuracy];
mShouldStopAndStartLocationServiceAgain = YES;
[update appendString:@"\n\n"];
// Altitude
if (signbit(newLocation.verticalAccuracy)) {
// Negative accuracy means an invalid or unavailable measurement
[update appendString:LocStr(@"AltUnavailable")];
} else {
// Positive and negative in altitude denote above & below sea level, respectively
[update appendFormat:LocStr(@"AltitudeFormat"), fabs(newLocation.altitude), (signbit(newLocation.altitude)) ? LocStr(@"BelowSeaLevel") : LocStr(@"AboveSeaLevel")];
[update appendString:@"\n"];
[update appendFormat:LocStr(@"MeterAccuracyFormat"), newLocation.verticalAccuracy];
[update appendString:@"\n\n"];
//geocoding implementation here........................................................................... .........................................
NSString *ServerUrl=@"http://maps.google.com/maps/geo?";
NSString *restUrl=@"output=csv&oe=utf8&sensor=false&key=ABQIAAAA9nyRoYg0rWpsiVi9iMjoSRQV WFT_Rez40XtsgfvlPpZQQeDyexSS5IUWt7S7bu53pG1lR3fjgcrfxQ";
NSString * URLdata=[NSString stringWithFormat:@"%@q=%f,%f&%@",ServerUrl,newLocation.coordinate.latitude,newL ocation.coordinate.longitude,restUrl];
NSURL *theURL = [NSURL URLWithString:URLdata];
NSURLRequest *myURLRequest = [NSURLRequest requestWithURL: theURL];
NSURLResponse* myURLResponse;
NSError* myError;
NSData* myDataResult = [NSURLConnection sendSynchronousRequest: myURLRequest returningResponse:&myURLResponse error:& myError];
NSString* StreetName;
BOOL val=YES;
StreetName = [[NSString alloc] initWithData:myDataResult encoding:NSASCIIStringEncoding];
//NSLog(@"this is the lenght of the street name %d",[StreetName length]);
if([StreetName length]!=0)
NSLog(@"this is the street name received.............. %@",StreetName);//[StreetName substringFromIndex:6]);
//NSMutableArray *street=[[StreetName substringFromIndex:6] componentsSeparatedByString:@","];
NSMutableArray street=(NSMutableArray*)(NSMutableArray)[StreetName componentsSeparatedByString:@","];
NSString *tempString=[street objectAtIndex:2];
appDel1.currentLocation=[tempString substringFromIndex:1];
NSRange range=[tempString rangeOfString:@" "];
if(range.location==NSNotFound)
val=NO;
//NSLog(@"this is the value of bool in false %d",val);
else
val=YES;
//NSLog(@"this is the vale of bool in true %d",val);
NSString *finalStreet;
NSString *temp2;
temp3=@" ";
if(!val)
finalStreet=[tempString substringFromIndex:1];
NSLog(@"this is the street name %@",finalStreet);
else
NSMutableArray temp1=(NSMutableArray)[tempString componentsSeparatedByString:@" "];
for(int i=1;i<[temp1 count];i++)
temp2=[temp1 objectAtIndex:i];
temp3=[[temp3 stringByAppendingString:@" "] stringByAppendingString:temp2];
finalStreet=[temp3 substringFromIndex:0];
NSMutableArray *speedValues=[appDel1 getSpeedValue:[finalStreet stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]]];
if([speedValues count]>0)
if(appDel1.moreThanOneSpeed==YES)
appDel1.maxSpeed=[appDel1 getSpeed:[finalStreet substringFromIndex:0] first:newLocation.coordinate.latitude second:newLocation.coordinate.longitude];
else
appDel1.maxSpeed=[[speedValues objectAtIndex:0]intValue];
//Calculate speed
CLLocationDistance distance;
double calSpeed;
NSTimeInterval difference;
//calculate distance and time elapsed only if we save old location
if(oldLocation != nil)
difference= [[newLocation timestamp] timeIntervalSinceDate:[oldLocation timestamp]];
distance = [newLocation getDistanceFrom:oldLocation];
else{
distance = 0.0;
calSpeed =(distance/difference)*2.23693629;
NSLog(@"Time elapsed is: %f", difference);
NSLog(@"Distance travelled is: %f", distance);
NSLog(@"Speed is: %f", calSpeed);
//save the latest newLocation for calculating the speed
oldLocation = [newLocation retain];
appDel1.distance=distance;
appDel1.time=timeDiff;
[self.delegate displaySpeed:oldLocation.coordinate.latitude second:oldLocation.coordinate.longitude third:newLocation.coordinate.latitude fourth:newLocation.coordinate.longitude];
if(appDel1.speed!=calSpeed)
appDel1.speed=calSpeed;
[appDel1 checkLimitAndSpeed];
the speed and distance returned is always zero as the latitude and longitude remains the same always it does not keep updating.
Thanks

Calculations to get correct EXIF GpsImgDirection depending on Orientation?

I took three photos with the iPhone 3GS, all standing in the same position and all facing east (i.e. 90º). When the button was on the right (Horizontal (normal) orientation), the direction in the EXIF tag (GpsImgDirection) is given as 351/1 or 351.
When the button was on the bottom (portrait or Rotate 90 CW orientation), the direction in the EXIF tag is given as 85/1 or 85. When the button was on the left (Rotate 180 orientation), the direction in the EXIF header is given as 194/1 or 194.
If I'm facing east for all photos, the direction should always be somewhere close to 90. Why not? And is there a calculation that needs to be made taking the orientation into consideration to get the accurate direction? Depending on the camera rotation/orientation, I seem to get a range of N/E/S/W values that don't necessarily correspond to the actual direction, and the calculation is not obvious to me. Any ideas?

Hello, I met the same problem.
I hold a web site showing photos' GPS tags on OpenStreetMap, of which name is MapPIN'on OSM. I started to draw GPSImgDirection tag but photos taken by iPhone 3G always point wrong directions about 90 degrees from the right directions of camera. Some are clockwise, the other are anti-clockwise.
I thought that it's because the compass always point at the top of the iPhone. The direction always different for 90 degrees from the camera axis. If data of accelerometers can be read, right GPSImgDirection would be calculated from the compass direction. It would be a software bug. I would like to ask developers to fix it though, does someone know where should I report it?

I am using iPhone 3GS. I am living in Saudi Arabia. I cannot find the directions with in GCC contries in the Navigation Application "COMPASS" of iphone. Can you please explain me how to work on it??

I am using iPhone 3GS. I am living in Saudi Arabia. I cannot find the directions with in GCC contries in the Navigation Application "COMPASS" of iphone. Only the map is displayed. I am not gtting the directions or information when I use it. Can you please explain me how to work on it??

See http://kb.mozillazine.org/Editing_configuration#How_to_edit_configuration_files
Add code to [http://kb.mozillazine.org/UserChrome.css userChrome.css] below the @namespace line.
<pre><nowiki>@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* only needed once */
#context-sendlink {display:none !important;}</nowiki></pre>
See also http://kb.mozillazine.org/Chrome_element_names_and_IDs

Compass direction - azimuth

Similar Messages

Maybe you are looking for