LinkedIn-Msg-ChatGPT-Part02

WIC EXIF columns commonly used for GPS (create these as site columns) Create Single line of text site columns with these internal names (create with the internal name first, then rename the display name if you want): wic_System_GPS_Latitude wic_System_GPS_Longitude wic_System_GPS_Altitude These are the exact WIC keys used in a working pattern to capture EXIF GPS values in SPO. Practical ‘pair’ columns (recommended) Even if you create the WIC columns, you’ll usually want friendly columns that users filter or search on, plus a place to keep the raw metadata for troubleshooting: Latitude (Single line of text) Longitude (Single line of text) Altitude (Single line of text) RawExifData (Multiple lines of text, unlimited length) UpdateEXIFMetadata (Yes/No, default Yes) That pattern is useful because you can capture whatever EXIF/WIC keys exist in RawExifData, then later parse or reprocess them as needed.

The text outlines a recommended approach for handling GPS metadata from images using WIC (Windows Imaging Component) EXIF fields in SharePoint Online (SPO). It specifies the creation of three site columns using exact internal names—wic_System_GPS_Latitude, wic_System_GPS_Longitude, and wic_System_GPS_Altitude—to align with WIC keys that reliably capture GPS data. It then suggests creating additional user-friendly “pair” columns (Latitude, Longitude, Altitude) along with a RawExifData column for storing complete metadata and an UpdateEXIFMetadata Yes/No field (default set to Yes). This pattern enables both easy filtering/searching and flexible troubleshooting or reprocessing of EXIF data.