Loading Profile...
Behaviour of uploaded geotagged pictures
It would be nice if uploaded pictures that contain geographical data in their exif would be treated different on brightkite:
- When a picture is taken within 300 meters of your checkin point, the placemark should state the place you checked in to. The photo should however be mapped using the geographical location in the exif data. The photo should be exported to flickr using it's own geographical data in the exif.
- When a picture is taken over 300 meters away from your checkin location, it should carry a placemark resembling the geographic data in the exif. It should completely overrule the location you're checked in to at the time.
(These could be pictues taken while you're on the move and don't feel like checking in to that specific piece of motorway or trainrail first, lol..)
This would replace the current handling of pictures which, regardless of them containing geographic data, get slapped on the checkin-location of brightkite, also when the picture is exported to flickr, , leading to generic spots on your brightkite- and flickr-map, when this could be more detailed..
The way brightkite handles geotagged photos should change for both website uploads as for e-mailed photos..
Thanks :)
- When a picture is taken within 300 meters of your checkin point, the placemark should state the place you checked in to. The photo should however be mapped using the geographical location in the exif data. The photo should be exported to flickr using it's own geographical data in the exif.
- When a picture is taken over 300 meters away from your checkin location, it should carry a placemark resembling the geographic data in the exif. It should completely overrule the location you're checked in to at the time.
(These could be pictues taken while you're on the move and don't feel like checking in to that specific piece of motorway or trainrail first, lol..)
This would replace the current handling of pictures which, regardless of them containing geographic data, get slapped on the checkin-location of brightkite, also when the picture is exported to flickr, , leading to generic spots on your brightkite- and flickr-map, when this could be more detailed..
The way brightkite handles geotagged photos should change for both website uploads as for e-mailed photos..
Thanks :)
I’m confident you like the idea ;)
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Carnager, we do like this idea. :)
There have been a couple of other requests for this, so it has been on our radar. We are not working on it it at the moment, as we have a few bigger projects taking up our resources, but we will look into this further once we get those out of the way.
It's not terribly hard to implement, it's just a matter of finding the best way to do it and maintain a good user experience.
I’m hopeful
-
Inappropriate?I just started a topic with basically this same request, then found this topic. I would LOVE to see this implemented!
EMPLOYEE
