Geotags not working for many months

  • 1
  • Question
  • Updated 5 years ago
Just noticed that geotags haven't worked in months and months even though I have it checked to set geotags.

Explore x2 8gb card

And now that I think about it this is somewhat related to the photos not getting sent to my computer.  Yep, even though I'm connected to the internet and downloading as I uploaded a photo via eye.fi I still get this message....


If I click NO, the photo will NEVER get sent to my computer and in eye.fi view it never gets uploaded completely to there.  Always that blue/white line underneath it showing delivery is in progress.  

So to get photos uploaded to my computer I have to set it not to geotag.

Along with the geotags FTP to my own site isn't working.  Yep, correct uname/pword and eye.fi can connect to it but it hasn't been delivered to my site.  This is a relatively new problem.
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 1
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
this looks like a firewall issue the eyefi card does not have a gps it records available wifi networks when the photo was taken and then sends this to eyefi servers at the time of transfer eyefi then look the known location of the wifi networks and geotags the images using this data. the dialog box is stating that the eyefi app cannot connect to the eyefi servers and therefore cannot do the lookup.
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Here's how it works.

I have geotagging enabled
I take a photo
I see it being transferred because it pops up in the lower right corner of my screen
The above box pops up
If I click "No" the photo NEVER gets sent to my computer. 
If I click "Yes" they instantly get sent to my computer but with no geotags.

Eye.fi's permissions are all set correctly in Windows firewall.
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
i have just tested this at my end with a 16gb pro x2 and my cards are connecting to eyefi servers and doing geo lookup via eyefi servers.. granted i didn't get any geotags but that was not for want of trying i just don't have enough known wifi nodes to get a fix for my images, but the main point is no message to say deliver without geotags.

[00:08] Assoc: BTHomeHub-2B04, bp 100, mac 60:a4:4c:29:24:10, c: 4, auth 4, rssi 36[00:08] Common Rates: 01B 02B 05B 06 09 11B 12 18 24 36 48 54 
[00:08] htCapInfo: 112d
[00:08] Cap: 0411
[00:08] AssocResp: chanAgi 0, shortpream 0, cf_pol 0, cf_rqst 0, priv 1, ibss 0, ess 1
[00:08] WPA Connected
[00:08] Start DHCP
[00:10] Starting scan for in-progress auto-deletes...
[00:10] Media used sectors utilization 5% vs threshold 20%.
[00:11] WLAN State: Configured
[00:11] Received DHCP address 192.168.1.179.
[00:11] Scan for pending photos...
[00:11] Fetching card settings from server...
[00:11] Listener probe starting...
[00:11] Fetched transfer mode 0x222 and geo enable 1 from server
[00:12] Probing for listener at 192.168.1.112:59278.
[00:12] Using probed IP address 192.168.1.112:59278 for agent.
[00:00] 
[00:00] Eye-Fi firmware 5.2011 May 14 2014 23:35:48 started (1), hardware revision 1, CID "R3BMWA:01:2e", 14844/32 MB, 00-18-56-67-9d-cb, 0x07
[00:01] Marvell 8786 firmware version 12.57.6.p54 running, xtal offset 1/1.
[00:01] Card is in desktop (0x222) transfer mode (timestamp 1440518420), geo-tagging is enabled, hotspots are disabled.

if your client is throwing the deliver without geotags message it means something is blocking the eyefi apps access to eyefi servers
(Edited)
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Steps I took.  Geotagging is enabled.

Took photo
I see it uploaded because I see thumbnail in lower right corner
Once it was 100% transferred immediately the box pops up asking about waiting for geotags
Take card out, put in computer, get a log, post it here

Posted quite a bit from log to help you deduce this.  Will wait for your assessment to take next step.

[00:00] Eye-Fi firmware 5.2010 Aug 27 2013 18:12:44 started (1), hardware revision 1, CID "DD4G8M:30:03", 7806/32 MB, 00-18-56-31-30-6b, 0x01[00:02] Marvell 8786 firmware version 12.57.6.p54 running, xtal offset 18/18.
[00:07] Card is in online and desktop (0xc022) transfer mode (timestamp 1441628130), geo-tagging is enabled, hotspots are enabled.
[00:07] Using sync mode AUTO.
[00:07] ---------------- SCAN-P -----------------------
[00:07] BGOPS 0 MaxDiv 0 FastClock 3 SpeedClass 6 cache-mode 2
[00:07] Flash: Samsung 8GB SLC 42nm, params: 3/3/0/8/0, fBd
[00:07] Starting scan of media directories...
[00:07] Done scanning for new media (detected 3446 MB in all media). Uploads not pending.
[00:07] Scan for pending photos...
[00:08] Scan for pending videos...
[00:08] Done scanning for all photos. Uploads not pending.
[00:10] Scan complete
[00:10] Scan in progress - skipping scan ()
[00:11] Deleted 4 expired breadcrumbs...
[00:11] Starting scan for in-progress auto-deletes...
[00:11] Media used sectors utilization 44% vs threshold 50%.
[00:16] Scan for pending photos...
[00:16] Scan for pending videos...
[00:17] Done scanning for all photos. Uploads not pending.
[00:00] 
[00:00] Eye-Fi firmware 5.2010 Aug 27 2013 18:12:44 started (1), hardware revision 1, CID "DD4G8M:30:03", 7806/32 MB, 00-18-56-31-30-6b, 0x01
[00:02] Marvell 8786 firmware version 12.57.6.p54 running, xtal offset 18/18.
[00:02] Card is in online and desktop (0xc022) transfer mode (timestamp 1441628130), geo-tagging is enabled, hotspots are enabled.
[00:02] Using sync mode AUTO.
[00:02] BGOPS 0 MaxDiv 0 FastClock 3 SpeedClass 6 cache-mode 2
[00:02] Flash: Samsung 8GB SLC 42nm, params: 3/3/0/8/0, fBd
[00:03] ---------------- SCAN-P -----------------------
[00:06] Scan complete
[00:06] Scan in progress - skipping scan ()
[00:07] Scan for pending photos...
[00:07] Scan for pending videos...
[00:07] Done scanning for all photos. Uploads not pending.
[00:09] Starting scan of media directories...
[00:10] Starting scan for in-progress auto-deletes...
[00:11] Done scanning for new media (detected 3446 MB in all media). Uploads not pending.
[00:11] Scan for pending photos...
[00:11] Media used sectors utilization 44% vs threshold 50%.
[00:12] Scan for pending videos...
[00:12] Done scanning for all photos. Uploads not pending.
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
And just a reminder, while I'm waiting for geotags the photo WILL NOT get sent to my computer.  Its sitting out there somewhere.

Just wondering, can you "hard reboot" an eye.fi card?  lol
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
im sorry my card log was misleading it wasn't meant to show anything other than i have geotagging enabled and i made a grammatical error in my first sentence its not the card that needs to be able to contact eyefi for geotagging to work, its the eyefi app upon receiving an image while geotagging is enabled that contacts eyefi and sends the wifi access point data to be analysed eyefi servers then send the geolocation data back to the eyefi app to be added to the image.

the problem is not with the card but with your eyefi pc apps ability to reach out to http://api.eye.fi/api/rest/agent/1.0/ this is the address used to geotag images by the eyefi app as seen in this snippit from the eyefi app log. and this is the reason the app is throwing the error message you have posted.

09/09/2015 07:01:30 00000a2c DETAIL  HttpConnection: Receiving request on keep-alive connection from 192.168.1.179:3873809/09/2015 07:01:30 00000a2c INFO    Checking the load to create additional workers, load 1, free workers 4 of 4
09/09/2015 07:01:30 0000096c INFO    HttpConnector: Processing connection from 192.168.1.179:38738
09/09/2015 07:01:30 0000096c WARN    Unknown Content-Type, skipping body data
09/09/2015 07:01:30 0000096c INFO    HttpConnectorBase: Processing request [/api/soap/eyefilm/v1/upload]
09/09/2015 07:01:30 0000096c INFO    Processing picture upload...
09/09/2015 07:01:30 0000096c INFO    FileSink::init: Thumbnail path: C:\Users\Fiona\AppData\Local\Eye-Fi\cache\thumbnail\00-18-56-67-9d-cb\2015\9\9\3eee34d9553cf7af1903c9fc05c75bfa
09/09/2015 07:01:30 0000096c DETAIL  Uploader::processRequest: Reading upload data...
09/09/2015 07:01:30 00000a24 DETAIL  Sending GEO lookup request to URL:http://api.eye.fi/api/rest/agent/1.0/?method=devices.getGeo&Mac=00-18-56-67-9d-cb&File=IMG_1...
09/09/2015 07:01:30 0000096c DETAIL  Uploader: Opening spool file for writing...
09/09/2015 07:01:30 0000096c INFO    FileSink::Fire_ImageUploadShowImage_Event: Thumbnail path addr 043aa738
09/09/2015 07:01:30 0000096c INFO    ImageNotificationWnd::Event_OnImageUploadThumbnail: 043aa738

you can find this log on your pc at c:\users\"username"\app data\roaming\eye-fi\eyefi.log

you may have to turn off "do not show hidden or system files or folders" to see the files in explorer 
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Grin, your card log wasn't misleading at all.  I pretty much didn't understand it!  LOL

I had realized it was the app that needed to contact another app (eye.fi) for the geotags.

I can reach http://api.eye.fi/api/rest/agent/1.0/  It asks you to sign in and I figure that uses a special eye.fi uname/pword combo.

So here's last nights lines from C:\Users\calcuttaman\AppData\Roaming\Eye-Fi

Hopefully you can understand both of those error codes and we can go from there.


09/09/2015 08:06:53 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '192.168.10.129'09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '172.24.0.1'
09/09/2015 08:07:01 00001eb4 WARN    Failed to leave multicast group, Error: 10049 - The requested address is not valid in its context
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '192.168.10.129'
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '172.24.0.1'
09/09/2015 08:07:01 00001eb4 WARN    Failed to leave multicast group, Error: 10049 - The requested address is not valid in its context
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '192.168.10.129'
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '172.24.0.1'
09/09/2015 08:07:01 00001eb4 WARN    Failed to leave multicast group, Error: 10049 - The requested address is not valid in its context
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '192.168.10.129'
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '172.24.0.1'
09/09/2015 08:07:01 00001eb4 WARN    Failed to leave multicast group, Error: 10049 - The requested address is not valid in its context
09/09/2015 08:07:01 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '192.168.10.129'
09/09/2015 08:07:03 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '172.24.0.1'
09/09/2015 08:07:03 00001eb4 INFO    Joining multicast group '224.0.0.251' on interface '192.168.10.129'
09/09/2015 08:07:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:07:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:07:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:08:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:08:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:08:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:09:04 00001eb4 INFO    ListenerEngineImpl::doIdleProcessing...
09/09/2015 08:09:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:09:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:09:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:10:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:10:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:10:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:11:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:11:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:11:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:12:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:12:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:12:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:13:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:13:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:13:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:14:04 00001eb4 INFO    ListenerEngineImpl::doIdleProcessing...
09/09/2015 08:14:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:14:10 00001d4c INFO    Will retry the upload after 1 minute...
09/09/2015 08:14:17 000001d4 NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: 81020006
09/09/2015 08:15:10 00001d4c NOTICE  Login failed for card: 00-18-56-31-30-6b, Error code: -2130575354
09/09/2015 08:15:10 00001d4c INFO    Will retry the upload after 1 minute...
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Ok, more news!

I had uninstalled and reinstalled before but that obviously hadn't helped.  Your mention of files in C:\Users\calcuttaman\AppData\Roaming\Eye-Fi got me to thinking.  I deleted all those files and also in C:\Users\calcuttaman\AppData\Roaming\Titanium\appdata\fi.eye.center

Reinstalled eye.fi helper and now I'm not getting the geotag error message!!! I'm at a friends house in WI and while its not giving me an exact location right now it does identify the city correctly.  

FTP still isn't working but that is not a big deal at all and I can do without that.
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
im just going to call you m28 for short :D but awesome news ill make a note that a clean reinstall maybe required next time someone hits this wall.

we can work on your ftp problem if you like, i dont mind.

Alan
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
I just took some photos and It didn't even get the city so I've got to play around with that part some more and see if I can get the geotags working 100%.  Will be out of touch for a few days so next week we can do the ftp.
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
eyefi card geotagging can be hit and miss as it does not actually use GPS eyefi explain it far better than i could. but in summary no wifi networks no geotag 

Using WPS to determine location
Eyefi cards use Wi-Fi Positioning System (WPS) for geotagging purposes. While similar, WPS is not the same as Global Positioning System (GPS), which is used in most location devices. WPS uses surrounding wireless networks to triangulate the location where the photo was taken, unlike GPS, which uses satellites.
Many things must happen for the latitude and longitude to end up in the EXIF data of a photo. First, a camera captures the photo. An Eyefi card detects any Wi-Fi networks in the area and records the MAC addresses of each one while not actually connecting to them. The MAC addresses are stored in the Eyefi card with the picture until it uploads the photo. Once the Eyefi card comes into contact with a configured wireless network and the photos begin transferring, the WPS data is sent to the Skyhook WPS service. At that time, the Skyhook WPS service translates and triangulates the WPS data to determine latitude and longitude. Skyhook then sends this information back to Eyefi's servers, which write the latitude and longitude to the photographs EXIF. At this point, the photo is delivered in its entirety to your computer or online photo sharing web site.


and the full FAQ can be found on this link https://x2help.eyefi.com/hc/en-us/articles/200112756-Geotagging-Overview

(Edited)
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Now that I read that I remember reading this awhile ago.  I just uploaded some of these same pics to Picassa and while it didn't get all of them to geotag it got quite a few of them.  More work on this next week.
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Interesting stuff to report.  I am back home in Sault Sainte Marie, MI.  I've played around taking photos at my house and all around town.  

I went back a few years in eye-fi center and it looks like geotags hasn't really worked for a long time!  I'm surprised that I never really looked at this before.  But I could have sworn they were working pretty good before!!!

I took some control photos while driving down the business spur in town.  In eye-fi center they do show up with a tag of Sault Sainte Marie.  BUT, they also say they weren't geotagged!

I uploaded those 3 control photos to PIcassa and they show up perfect on PIcassa's map.



Now a little bit of weirdness in eye-fi center.  Will use the DQ photo to show you.  If you click on the i button for more info this is what you see.



Now if you use the latitude and longitude above it places it correctly in Google Maps.  Those numbers for easy testing are: 46°28'47.26"N, 84°21'13.54"W

Typically it shows a upside down reddish tear drop in eye-fi center when a photo ISN'T geotagged.  I just went back in eye-fi center to 2010 and looked at all my old photos.  I can find tons of photo that DON'T have the red teardrop (When there is no red teardrop there is a white arrow with blue background) and when I've clicked on the arrow they say they weren't geotagged.

Hypothesis:  Those old photos used to show exactly where the photos were taken.  I believe that sometime in the last 1 month to maybe a couple of years something went haywire and eye-fi itself took the geotags away!

Maybe it coincided with this press release from 4-6-2014...
We apologize, but as of September 9, 2013, Geotagging is no longer available as an add-on service. If you have purchased an Eyefi card that includes the Geotagging service, it will still be supported and you can enable it in your Eyefi Center account when you initialize your card.

So Alan.  Does your geotags show exact positions of where photos were taken?
 
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
I double dog dare someone from Eye-Fi to comment on this thread!  LOL
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
im not actually eyefi, but i have been around a very long time geotagging was discontinued i think partially because it was never 100% reliable, like i say its not GPS tagging the eyefi card records details such as the mac address and SSID of wireless networks it finds when you take a shot this information is sent to eyefi while uploading images and then it is used by i think it was Skyhook to find the nearest geolocation for your photos so..... no wifi networks around, very definitely no! geotag and even with wifi networks in range the networks location has to be known by skyhook for geotagging to occur. customer satisfaction with this geotagging method was never perfect and with mobile app geotagging on android and a desire to introduce this feature on IOS (they never did get round Apple's limits on geo data) there was no longer any need for WPS geotagging and this s why geotagging was dropped in september 2013 but it was only dropped in as much as you couldn't purchase it as an extra it still works exactly as it did for cards that included the feature in the purchase price such as the x2 explore and the x2 pro. i would say that Skyhook's database is most likely getting old with people replacing wifi routers for faster more modern devices. in fact my own router at home provided by my isp used to get me geotags but having replaced it for one i purchased i no longer get geotags at home.

so im sorry to say there are no conspiracy theories here just technology moving on......

oh and eyefi don't touch the data in your photos once they are uploaded so they don't remove geotags that have already been applied.
(Edited)
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
I never meant it in any way shape or form as a conspiracy.  And I guess I didn't word this very well, "...something went haywire and eye-fi itself took the geotags away"

Alan, when I first got this eye-fi card it could locate photo pretty good and I'm sure that there were quite a few of my photos in eye-fi helper that showed the exact locations.  

I guess what I was trying to say was the exact locations were there before, albeit in at least 2010 & 2011 but now they aren't even showing at all.   Can you go back a few years in your eye-fi helper and see if you have any exact locations.  Maybe before your newest router?

Interesting to note that driving my car down a business spur and taking 3 random photos that Picassa got it right.  Guess with the Google $ behind them.  Grin

Speaking of PIcassa, they grab the lat/long out of the exif data in my photo that's stored on my eye-fi card.  

And here's the million dollar question, my photos I took today HAD the lat/long embedded in them.  So should eye-fi JUST display the city name, or should it give the exact location.

Hoping others besides Alan can answer that.
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
im sorry i didnt mean to sound rude either and i hope you didn't take it that way i try to reread everything before posting to ensure i have used the appropriate tone 

i checked back and the last images taken at home with a geotag was at the end of january this year the odd thing is i have had my router for way longer than that so maybe i was getting tags from a neighbors router who has now moved away however i have been moving steadily towards an entirely Mobi workflow for my personal photos so my last vacation did not get any geotags. and i have not used my x2 cards for at least a couple of months other than for assisting others with problems.

further checking back through 2014 shows geotagging to be consistent in that i only get geotags in urban areas and only at specific locations say a person's house will always get a geotag but other people's houses consistently did not get geotagged that is until the end of january when i have not got a single geotag at home or otherwise. i tend to shoot in places with no wifi around at all such as on top of mountains. 



like i say it's more likely skyhooks data is becoming more inaccurate and out of date. speculating further its possible that eyefi and skyhook were aware that this was likely to take place and decided to withdraw the service at that time rather than continue selling the service.
(Edited)
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
When you say you got geotags in urban areas do you mean like around a lot of businesses?  When you click the the white arrow on blue or red teardrop does it show actual streets?
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
one thing i can say for sure is i went to legoland in a shopping mall in manchester and i fully expected to get geotags im pretty sure we used the x2 cards we didn't get any. i did get some geotags on images shot in public houses (bars to you, pubs here in the uk) in january this year although some where way off target and not even in the right town some other images in january had geotags hundreds of miles off target (maybe someone moved house and took their router with them) actually again the images i was looking at last year are again listed as being in the next town about 30 miles away from where they were took. in 2013 the accuracy is better but still not brilliant at least the tags are in the correct town and mostly just off by a couple of streets so i agree accuracy is getting a lot worse.
Photo of Alan Hinchcliffe

Alan Hinchcliffe, Champion

  • 378 Posts
  • 42 Reply Likes
when i can remember i use a little device called a mobile action gps logger that i leave on while im out and about and as i have done today i geotag my photos before importing into lightroom and so long as my clock is correct and my geotagger is on and i have remembered to bring it i get bob on accurate geotags. its just its so small i tend to loose t(put it away safely) just before i go on vacation or an important photowalk. 
Photo of Doug Garn

Doug Garn

  • 22 Posts
  • 0 Reply Likes
Alan, I'm very surprised you didn't get a geotag in Legoland!  Consider that I got geotagged with 3 photos over a 2 mile stretch of road driving 40 mph!!!  How good is that?
Photo of Doug Garn

Doug Garn

  • 22 Posts
  • 0 Reply Likes
I guess I'm over it that eye-fi helper can't show me a street level map like PIcassa.  
Curious, as eye-fi is the one that is providing me the lat/long and writing that into the exif data. 
(Edited)
Photo of Doug Garn

Doug Garn

  • 22 Posts
  • 0 Reply Likes
BTW, you jarred my memory with Skyhook.  Here's an old press release, http://www.wi-fiplanet.com/news/article.php/3746346/

Also, do you remember EasyWifi?  Here's some articles...
https://x2help.eyefi.com/hc/en-us/articles/200127506-EasyWiFi-and-X2-Hotspot-Access
https://x2help.eyefi.com/hc/en-us/articles/200091957-Add-an-Easy-WiFi-Hotspot-Account

EasyWifi was very helpful 4-5 years ago when there was quite a few places that still charged for wifi access.  Starbucks was one of those.  Also, it could get around some splash screens.  

EasyWifi is no more, I think it changed to Wayport and then got absorbed by ATT (But I could have that all wrong).

Grin.  I have all 32 spots filled on my network access and I used to have a EasyWifi account with many networks attached to that.  They were mostly all default usernames and passwords for all the routers out there!  LOL
Photo of Doug Garn

Doug Garn

  • 22 Posts
  • 0 Reply Likes
Late breaking news..............

Was playing around with http://center.eye.fi

And what do you know, it CAN display exact locations!!!!!!!!!!!!!!

Photo of Lee

Lee

  • 2 Posts
  • 0 Reply Likes
I have this exact same issue with my X2 Pro 8GB.  It transfers fine, but geotagging hasn't worked for almost a year now.  I also have an Eye-fi Explore Video card, and taking pictures in the same place with the same camera Nikon D90, geotagging works.  I can't see any errors in the logs.  Not sure how to fix this.  
Photo of m28us41 .

m28us41 .

  • 13 Posts
  • 0 Reply Likes
Alan,

Been having ongoing emails with eye.fi support over this.  It works for them but not me!  Does it work for you?  It should look like the attached.
Photo of Lee

Lee

  • 2 Posts
  • 0 Reply Likes
I don't think this can be a Skyhook issue if the geotagging works consistently with my older Eye-fi Explore card but doesn't work anymore with my X2 card.  So frustrating that this is still a problem.  This experience has soured me on eye-fi and I'm no longer recommending them to family and friends.