[Geotiff] Re: [OSGeodata] File format for geo-coded ground-based photos
djdenk at gmail.com
Wed May 10 20:59:12 EDT 2006
You might also want to look through Adobe's XMP [Extensible Metadata
Platform] integrated into Photoshop versions CS and newer - and see if
there's anything of use.: http://www.adobe.com/products/xmp/indepth.html
Unfortunately, XMP forces you away from EXIF - and since it's not an actual
standard I don't and wouldn't use it because of this.
Kodak, Nikon, and Canon, may have relative source materials in regards to
their metadata platforms as well. They might be the best source in that
regard - though keep in mind that there's been a movement in the camera
industry to encrypt useful information - rendering the metadata somewhat
useless unless you're only using their software tools. Also keep in mind
that each camera/sensor model can have its own metadata platform. This is
why we see so many different flavors of plugins and formats to handle one
camera over another, blah blah, yada.
It seems everyone and their mom wants their own proprietary method these
That statement aside -- here's an example of how designers are generating a
'movement' into geo-located concepts with photography and other imagery
source media [video, for example]. I believe this example simply uses
standard XML markup, which is of course a far more standard approach. Put
this concept in the reality of the Web 2.0, Identity 2.0, and Business
2.0paradigm movement, you can begin to gauge why designers are so
Mix mobile applications in that mess and you'll see why all the fuss. This
is a Flash interface - which I consider non-standard [another that falls
within the 'Industry Standard' paradigm as it's a plugin], but the work
being done with AJAX is phenominal and progressing rapidly as well.:
You can also look into stuff like this, just because it's so darn cool. (Uh
oh, my geek is showing!):
On 5/10/06, Jo Walsh <jo at frot.org> wrote:
> dear Ned, all,
> On Wed, May 10, 2006 at 12:06:46PM -0400, Ned Horning wrote:
> > The information stored with the photo data should include camera state
> > (focal length, date, time, frame size, resolution),
> > location (geographic coordinates), and orientation (camera bearing,
> > and possibly camera inclination) information.
> > Would it make sense to extend the GeoTIFF format?
> On Wed, May 10, 2006 at 09:44:07AM -0700, Tyler Mitchell wrote:
> > Ned,
> > EXIF already has some stuff, of course. I assume you've seen this..
> It looks as if EXIF expresses almost everything that you need already,
> apart from camera inclination.
> http://www.exif.org/forum/topic.asp?TOPIC_ID=12 offers suggestions for
> extra inclination properties in the 'EXIF GPS IFD'
> http://akuaku.org/archives/2003/05/gps_tagged_jpeg.shtml talks about
> extracting GPS information from EXIF headers where it's supplied, and
> there are some useful links in the comments.
> I'm not sure whether you are looking for embedded, or external,
> metadata for your imagery; are you looking to make the photo metadata
> available separately? If so, there was some work at the w3c on a
> schema for EXIF that could be used with GeoRSS, RDF or any flavour of XML:
> Isn't there also some of JPEG2000 / GML work going on through the OGC?
> Michael Gerlek is involved in this and might be able to let you know
> whether this is fit for your purposes and what the tradeoffs with EXIF
> might be.
> > If a new standard needs to be developed how does one begin that
> > process. Would the geodata committee of OSGeo be a good start?
> If there is a question of wanting to propose extensions to a standards
> maintainer like JEITA, and it would add weight for a proposal to come
> from formally from OSGeo, then I think this would be appropriate for
> us to put forward. Hopefully this is at least a good place for members
> to put out feelers towards people who are more expert in any given
> Geotiff mailing list
> Geotiff at lists.maptools.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Geodata