Image file formats support in arkimet #277

brancomat · 2021-11-09T14:47:53Z

As discussed in other fora, arkimet capabilities should be extended for archiving and indexing image file formats (i.e.: webcam outputs).

As a starting point it shoud support:

jpeg for image format
exif for metadata

A minimal set of metadata to index could be:

reftime ("Date and Time")
Latitude/Longitude
dimensions ("Pixel X Dimension", "Pixel Y Dimension")

Sample image: test.tar.gz

It would be nice if the resulting scanner could be accompanied by some documentation, to facilitate independence in metadata extensions / edits.

(this is a working draft, open to suggestions)

pat1 · 2021-11-09T15:26:32Z

in RMAP I use
Latitude/Longitude, reftime, imagedescription,usercomment

https://github.com/r-map/rmap/blob/0ef0ce01ecf0e88b7530e1d09cc303fa53db473e/python/rmap/exifutils.py#L153
but usercomment is not usefull as arkimet metadata (I am not sure!).

The dimensions I think are not usefull metadata too.

I use imagedescription to identify the provider of image (is the only standard exif metadata I found usefull for this) but is possible to change it.

So I suggest those minimal metadata for arkimet:
Latitude/Longitude, reftime, imagedescription

those are the linked exif metadata:

ImageIFD.ImageDescription
ImageIFD.DateTime
GPSIFD.GPSLatitude
GPSIFD.GPSLongitude
GPSIFD.GPSLatitudeRef

dcesari · 2021-11-09T15:43:10Z

In @brancomat example we have also altitude -> station height, although that's not usually metadatum (using jhead):

GPS Latitude : N **d 30m  2.7179s
GPS Longitude: E **d 19m 43.2263s
GPS Altitude :  98.00m

pat1 · 2021-11-09T19:14:34Z

for the webcam network we need other metadata.
For example:

they can be mean in time (timerange)
the height from the soil (level)
the cardinal direction where we look at
the channel (visible, IR)

spanezz · 2021-11-23T14:21:19Z

Do you expect to need to have a dataset with hybrid image formats, like .png and .jpg?

brancomat · 2021-11-23T14:43:59Z

I'd say no.
The dataset content format should be consistent (as in any other arkimet dataset). Should we face multiple source formats, either the import procedure should standardize the format or we could create different datasets based on image format.

spanezz · 2021-11-23T14:45:26Z

Ok, perfect. Mixing different formats in the same dataset would require a significantly more extensive redesign work

…tion. refs: #277

spanezz · 2021-11-24T14:06:20Z

We have initial JPEG support:

$ gzip -cd test/data/jpeg/autumn.jpg.gz > /tmp/autumn.jpg
$ arki-scan --yaml /tmp/autumn.jpg 
Source: BLOB(jpeg,/tmp/autumn.jpg:0+94701)
Reftime: 2021-10-24T13:11:40Z
Area: GRIB(latfirst=459497, latlast=459497, lonfirst=110197, lonlast=110197, type=0)
Note: [2021-11-24T14:02:36Z]Scanned from autumn.jpg

The scanning script is in conf/scan/jpeg.py and is a draft: in particular, the area should be a point, but not knowing how to represent a point I used a rectangle collapsed into a point just to make a demo.

Most of the pieces should be there to start a JPEG dataset. We now need real-world test samples to fine tune the scanner, and see if the existing metadata types are ok or we neeed to add new ones

pat1 · 2021-11-24T19:33:45Z

Most of the pieces should be there to start a JPEG dataset. We now need real-world test samples to fine tune the scanner, and see if the existing metadata types are ok or we neeed to add new ones

@spanezz can you describe the metadata ?

spanezz · 2021-11-25T12:35:18Z

I don't know if we have ever compiled a complete census of all metadata available in arkimet: the variety grew quite organically.

It may be time to do it, and it's a non trivial amount of work that would warrant its own ticket.

Can you (plural you) confirm that we don't have that documentation, and it's not that we actually have it and I cannot find it, and then open a ticket asking for it?

dcesari · 2021-11-25T14:53:52Z

Coming back to a previous message

We have initial JPEG support:
Area: GRIB(latfirst=459497, latlast=459497, lonfirst=110197, lonlast=110197, type=0)
The scanning script is in conf/scan/jpeg.py and is a draft: in particular, the area should be a point, but not knowing how to represent a point I used a rectangle collapsed into a point just to make a demo.

Why can't we use

Area: GRIB(lat=3993000, lon=971000)

as it is done for BUFR stations (although it says GRIB)?

pat1 · 2021-11-25T16:39:44Z

I don't know if we have ever compiled a complete census of all metadata available in arkimet: the variety grew quite organically.

I ask for JPEG only dataset.
@spanez ask:

if the existing metadata types are ok or we neeed to add new ones

which "existing metadata types"?

dcesari · 2021-11-26T08:12:44Z

see above:

$ gzip -cd test/data/jpeg/autumn.jpg.gz > /tmp/autumn.jpg
$ arki-scan --yaml /tmp/autumn.jpg 
Source: BLOB(jpeg,/tmp/autumn.jpg:0+94701)
==> Reftime: 2021-10-24T13:11:40Z
==> Area: GRIB(latfirst=459497, latlast=459497, lonfirst=110197, lonlast=110197, type=0)
Note: [2021-11-24T14:02:36Z]Scanned from autumn.jpg

spanezz · 2021-11-26T12:27:38Z

Area: GRIB(latfirst=459497, latlast=459497, lonfirst=110197, lonlast=110197, type=0)
Why can't we use
Area: GRIB(lat=3993000, lon=971000)
as it is done for BUFR stations (although it says GRIB)?

Good catch. I pushed the change, now it's the same as with BUFR

spanezz · 2021-11-26T12:38:06Z

I don't know if we have ever compiled a complete census of all metadata available in arkimet: the variety grew quite organically.
I ask for JPEG only dataset

The scanner for JPEG datasets can generate any metadata value that is used by all other scanners: arkimet doesn't have a concept of format-specific metadata.

Sometimes the name of a format makes it to metadata values, like in product:GRIB,…, product:BUFR,…, and that means that the product is described with a given set of values that follow the rules for product definitions in GRIB or BUFR standards.

if the existing metadata types are ok or we neeed to add new ones
which "existing metadata types"?

I mean all the metadata available in arkimet for all other formats: can they be reused to describe everything needed for a JPEG, or do we need to create new ones? That's not something that we can answer up front, I think, and we'll see as we start putting real world data into a dataset, and figuring out what are the aspect of those data that we want to be able to query with arkimet

edigiacomo · 2023-06-21T08:01:07Z

camera_pan: preso come fulcro la telecamera l'angolo formato partendo da nord in verso orario del il punto al centro dell'immagine espresso in gradi sessadecimali senza decimali; valori 0-359

camera_tilt: zero piano orizzontale, positivo verso il cielo, negativo verso terra, espresso in gradi sessadecimali senza decimali

camera_roll: zero piano verticale, zero in alto, l'angolo formato dalla rotazione dell'immagine positivo in senso orario, negativo antiorario

Questi metadati potrebbero essere tra gli standard:

0xb20b | 45579 | MpfInfo | Exif.MpfInfo.MPFYawAngle | Long | MPF Yaw Angle
0xb20c | 45580 | MpfInfo | Exif.MpfInfo.MPFPitchAngle | Long | MPF Pitch Angle
0xb20d | 45581 | MpfInfo | Exif.MpfInfo.MPFRollAngle | Long | MPF Roll Angle

Per quanto riguarda il livello, mi sfugge perché le informazioni GPS non possono essere usate:

0x0005 | 5 | GPSInfo | Exif.GPSInfo.GPSAltitudeRef | Byte | Indicates the altitude used as the reference altitude. If the reference is sea level and the altitude is above sea level, 0 is given. If the altitude is below sea level, a value of 1 is given and the altitude is indicated as an absolute value in the GSPAltitude tag. The reference unit is meters. Note that this tag is BYTE type, unlike other reference tags.
0x0006 | 6 | GPSInfo | Exif.GPSInfo.GPSAltitude | Rational | Indicates the altitude based on the reference in GPSAltitudeRef. Altitude is expressed as one RATIONAL value. The reference unit is meters.

Rimarrebbero, a quel punto, solo channel, timerange (e level, se quello del GPS non va bene).

edigiacomo · 2023-06-21T09:55:16Z

@pat1 te la riassegno per una review.

pat1 · 2023-06-21T10:38:20Z

Per quanto riguarda il livello, mi sfugge perché le informazioni GPS non possono essere usate

secondo me per compatibilità con tutto il resto e per indiscussa versatilità del sistema WMO e inoltre l'altitudine usata come riferimento non mi è chiarissimo come usarla. Ma se è conforme usarla come:

GPSAltitudeRef: altitudine del suolo da MSL
GPSAltitude: sltitudine del sensore da GPSAltitudeRef

ma secondo me essendo da GPS si intende tutt'altro.

Channel nelle immagini pare abbia un altro significato lo sostituirei con "spectral band" o sinteticamente "band"
e potrebbe essere declinato in:

VIS: visibile
VIR: Infrarosso vicino al visibile, non termometrico utilizzato per fotografia IR e riflettografia;
SW: Infrarosso onda corta, adatto a misure di temperature elevate (es.controllo combustione forni);
MW: Infrarosso medio, utilizzato di norma come confronto per altre frequenze per l'identificazione oggetti o gas es. spettrografia e immagini satellitari
LW: Infrarosso lontano, la banda più comunemente utilizzata adatta alle misure vicine alle temperature ambientali utilizzata in tutte le applicazioni terrestri
XLW: Infrarosso verso microonde: adatta per l'osservazione di temperature inferiori a 250 K, utilizzata per osservazioni astronomiche.

oppure:

NUV : Near ultraviolet,visible
NIR : Near infrared
MIR: Mid infrared
FIR: Far infrared

edigiacomo · 2023-06-21T10:45:04Z

ma secondo me essendo da GPS si intende tutt'altro.

Ok, allora manteniamo il level dentro allo UserComment così siamo a posto.

Channel nelle immagini pare abbia un altro significato lo sostituirei con "spectral band" o sinteticamente "band"

Sul channel benissimo tramutarlo in band, ma io non ho idea di cosa si stia parlando, quindi scegli pure tu quali valori usare.

Non ho invece capito se

0xb20b | 45579 | MpfInfo | Exif.MpfInfo.MPFYawAngle | Long | MPF Yaw Angle
0xb20c | 45580 | MpfInfo | Exif.MpfInfo.MPFPitchAngle | Long | MPF Pitch Angle
0xb20d | 45581 | MpfInfo | Exif.MpfInfo.MPFRollAngle | Long | MPF Roll Angle

Possono andare bene oppure vogliamo metterli come metadati custom camera_pan, camera_roll e camera_tilt?

pat1 · 2023-06-21T12:51:14Z

Non ho invece capito se
0xb20b | 45579 | MpfInfo | Exif.MpfInfo.MPFYawAngle | Long | MPF Yaw Angle
0xb20c | 45580 | MpfInfo | Exif.MpfInfo.MPFPitchAngle | Long | MPF Pitch Angle
0xb20d | 45581 | MpfInfo | Exif.MpfInfo.MPFRollAngle | Long | MPF Roll Angle
Possono andare bene oppure vogliamo metterli come metadati custom camera_pan, camera_roll e camera_tilt?

LONG è definito come 32-bit (4-byte) unsigned integer il che è già un problema perchè bisogna inventarsi una rappresentazione unsigned.
Poi quei tag fanno parte di:

MPF Tags
These tags are part of the CIPA Multi-Picture Format specification, and are found in the APP2 "MPF" segment of JPEG images.

Multi-Picture Format
The file format includes MP extensions which enable to store multiple Individual Images
in a single file. Individual Image has the same structure as Exif JPEG data.

quindi direi non c'entrano nulla con il nostro caso.

pat1 · 2023-06-21T13:07:13Z

riassumendo oltre ai tag exif per lat, lon,datetime :

Per i metadati custom usare il tag User Comment in cui mettere un JSON con dentro i metadati.
La proposta è di usare una sintassi del genere:

User Comment = COMMENTO {% METADATI %} COMMENTO

L'elenco dei metadati è il seguente:

Per il timerange usiamo la sintassi dballe [pindicator, p1, p2]
Per il livello usiamo la sintassi dballe [leveltype1,l1,leveltype2,l2]
Per il product indicare quattro chiavi

camera_band
camera_pan
camera_tilt (opzionale)
camera_roll (opzionale)

"band"
e potrebbe essere declinato in:

VIS: visibile
VIR: Infrarosso vicino al visibile, non termometrico utilizzato per fotografia IR e riflettografia;
SW: Infrarosso onda corta, adatto a misure di temperature elevate (es.controllo combustione forni);
MW: Infrarosso medio, utilizzato di norma come confronto per altre frequenze per l'identificazione oggetti o gas es. spettrografia e immagini satellitari
LW: Infrarosso lontano, la banda più comunemente utilizzata adatta alle misure vicine alle temperature ambientali utilizzata in tutte le applicazioni terrestri
XLW: Infrarosso verso microonde: adatta per l'osservazione di temperature inferiori a 250 K, utilizzata per osservazioni astronomiche.

oppure:

NUV : Near ultraviolet,visible
NIR : Near infrared
MIR: Mid infrared
FIR: Far infrared

camera_pan
camera_tilt
camera_roll

Camera angles: pan, tilt, roll

definendo:
camera_pan:
preso come fulcro la telecamera l'angolo formato partendo da nord in verso orario del il punto al centro dell'immagine espresso in gradi sessadecimali senza decimali; valori 0-359

camera_tilt:
zero piano orizzontale, positivo verso il cielo, negativo verso terra, espresso in gradi sessadecimali senza decimali

camera_roll:
zero piano verticale, zero in alto, l'angolo formato dalla rotazione dell'immagine positivo in senso orario, negativo antiorario

Il JSON sarebbe quindi una cosa del genere:

{
    "timerange": [254, 0, 0],
    "level": [103, 2000, null, null],
    "product": { "camera_band": "VIS", "camera_pan": -78,"camera_roll":0}
}

La conversione in metadati arkimet potrebbe essere:

Per il timerange, lo stile Timedef
Per il livello, lo stile GRIB1
Per il product, si può usare proddef con stile GRIB1

edigiacomo · 2023-06-21T13:08:02Z

Per me va benissimo

dcesari · 2023-06-21T13:52:10Z

Siete dei maghi! Aggiungo solo che la classificazione VIS, VIR,... SLW mi pare più adatta per definire la banda perché pare orientata alle applicazioni fotografiche e affini, mentre l'altra classificazione è più fisica, e la banda effettivamente usata potrebbe essere "a cavallo" tra 2 definizioni; però parlo un po' a sentimento.

edigiacomo · 2023-06-21T15:35:18Z

Le spefiche sono state trasmesse alla ditta che dovrà generare i file JPEG. Attendiamo, per il proseguimento del lavoro, un file di test da parte loro.

@spanezz ti avviso non appena me lo inviano.

edigiacomo · 2023-11-30T12:55:59Z

Assegno la issue a @pat1 (si veda e-mail "Tag EXIF per progetto camERa" di oggi) che dovrebbe verificare la correttezza dei tag EXIF nei file JPEG che la ditta ci sta mandando per poterteli poi passare.

edigiacomo · 2024-01-23T10:59:28Z

Allego le specifiche v0.1 del progetto camERa Progetto camERa_ specifiche EXIF tag - v0.1.pdf.

Per ora, i metadati che sono sicuramente da implementare sono:

Coordinate
Reftime
Timerange

@pat1 allegherà poi dei file JPEG di esempio per la test suite.

pat1 · 2024-01-30T17:11:31Z

Nomenclatura file riportata qui per comodità

Telecamere

NOME	Codice
RICCIONE (IAL RICCIONE)	1
VALVERDE (IAL CESENATICO)	2
PRESTIGE	3
CESENATICO (B&B SOLEE)	4
MARINA DI RAVENNA (BAGNO MARISOL)	5
LIDO DI SPINA (BAGNO MARRAKESH)	6
MARINA ROMEA (BAGNO NETTUNO)	7
LIDO DI VOLANO (BAGNO CORMORANO)	8

Prodotti

ST rappresenta il codice telecamera

TIMEX: TIMEX_ST_YYYYMMDD_hhmm
Immagine orto rettificata: RECTM_ST_YYYYMMDD_hhmm
TIMESTACK: T1STK_ST_YYYYMMDD_hhmm
Linea di riva su TIMEX: TMXSH_ST_YYYYMMDD_hhmm
Linea di riva su immagine rettificata: RECSH_ST_YYYYMMDD_hhmm
Snapshot: SNAPSHOT_ST_YYYYMMDD_hhmm

pat1 · 2024-01-30T18:44:07Z

Allego immagini di esempio. innagini.zip
I metadati contenuti di livello e timerange non hanno contenuto sostanziale corretto ma formalmente si.
Questi i metadati:

for file in  [innagini.zip](https://github.com/ARPA-SIMC/arkimet/files/14102836/innagini.zip); do printf  "\nExif info fron file: $file"; exiv2 -p a -u  $file; done

Exif info fron file: RECSH_1_20240129_1200.jpgWarning: Directory Photo has an unexpected next pointer; ignored.
Warning: Directory GPSInfo has an unexpected next pointer; ignored.
Exif.Image.ExifTag                           Long        1  38
Exif.Photo.UserComment                       Undefined 224  charset=Unicode {% {"timerange": [205, 0, 900], "level": [264, null, null, null], "camera_pan": 40,  ...
Exif.Image.GPSTag                            Long        1  276
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  North
Exif.GPSInfo.GPSLatitude                     Rational    3  43deg 59' 20"
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  12deg 41' 2"
Exif.GPSInfo.GPSTimeStamp                    Rational    3  12:00:00
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2024:01:29

Exif info fron file: RECTM_1_20240129_1200.jpgWarning: Directory Photo has an unexpected next pointer; ignored.
Warning: Directory GPSInfo has an unexpected next pointer; ignored.
Exif.Image.ExifTag                           Long        1  38
Exif.Photo.UserComment                       Undefined 224  charset=Unicode {% {"timerange": [205, 0, 900], "level": [264, null, null, null], "camera_pan": 40,  ...
Exif.Image.GPSTag                            Long        1  276
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  North
Exif.GPSInfo.GPSLatitude                     Rational    3  43deg 59' 20"
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  12deg 41' 2"
Exif.GPSInfo.GPSTimeStamp                    Rational    3  12:00:00
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2024:01:29

Exif info fron file: SNAPSHOT_1_20240129_1200.jpgWarning: Directory Photo has an unexpected next pointer; ignored.
Warning: Directory GPSInfo has an unexpected next pointer; ignored.
Exif.Image.ExifTag                           Long        1  38
Exif.Photo.UserComment                       Undefined 220  charset=Unicode {% {"timerange": [254, 0, 0], "level": [264, null, null, null], "camera_pan": 40, "c ...
Exif.Image.GPSTag                            Long        1  272
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  North
Exif.GPSInfo.GPSLatitude                     Rational    3  43deg 59' 20"
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  12deg 41' 2"
Exif.GPSInfo.GPSTimeStamp                    Rational    3  12:00:00
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2024:01:29

Exif info fron file: T1STK_1_20240129_1200.jpgWarning: Directory Photo has an unexpected next pointer; ignored.
Warning: Directory GPSInfo has an unexpected next pointer; ignored.
Exif.Image.ExifTag                           Long        1  38
Exif.Photo.UserComment                       Undefined 224  charset=Unicode {% {"timerange": [205, 0, 900], "level": [264, null, null, null], "camera_pan": 40,  ...
Exif.Image.GPSTag                            Long        1  276
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  North
Exif.GPSInfo.GPSLatitude                     Rational    3  43deg 59' 20"
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  12deg 41' 2"
Exif.GPSInfo.GPSTimeStamp                    Rational    3  12:00:00
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2024:01:29

Exif info fron file: TIMEX_1_20240129_1200.jpgWarning: Directory Photo has an unexpected next pointer; ignored.
Warning: Directory GPSInfo has an unexpected next pointer; ignored.
Exif.Image.ExifTag                           Long        1  38
Exif.Photo.UserComment                       Undefined 220  charset=Unicode {% {"timerange": [0, 0, 900], "level": [264, null, null, null], "camera_pan": 40, "c ...
Exif.Image.GPSTag                            Long        1  272
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  North
Exif.GPSInfo.GPSLatitude                     Rational    3  43deg 59' 20"
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  12deg 41' 2"
Exif.GPSInfo.GPSTimeStamp                    Rational    3  12:00:00
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2024:01:29

Exif info fron file: TMXSH_1_20240129_1200.jpgWarning: Directory Photo has an unexpected next pointer; ignored.
Warning: Directory GPSInfo has an unexpected next pointer; ignored.
Exif.Image.ExifTag                           Long        1  38
Exif.Photo.UserComment                       Undefined 224  charset=Unicode {% {"timerange": [205, 0, 900], "level": [264, null, null, null], "camera_pan": 40,  ...
Exif.Image.GPSTag                            Long        1  276
Exif.GPSInfo.GPSLatitudeRef                  Ascii       2  North
Exif.GPSInfo.GPSLatitude                     Rational    3  43deg 59' 20"
Exif.GPSInfo.GPSLongitudeRef                 Ascii       2  East
Exif.GPSInfo.GPSLongitude                    Rational    3  12deg 41' 2"
Exif.GPSInfo.GPSTimeStamp                    Rational    3  12:00:00
Exif.GPSInfo.GPSDateStamp                    Ascii      11  2024:01:29

pat1 · 2024-01-31T09:04:08Z

visti i dati forniti dalla rete Camera propongo i seguenti adattamenti alle specifiche di codifica:

distinzione canale visibile tra RGB eBW nella tabella per camera_band:

VISR_GB: visibile con segnale RGB (red, green, blue)
VIS_BW: visibile con segnale BW (black and wite)
VIR: Infrarosso vicino al visibile, non termometrico utilizzato per fotografia IR e riflettografia;
SW: Infrarosso onda corta, adatto a misure di temperature elevate (es.controllo combustione forni);
MW: Infrarosso medio, utilizzato di norma come confronto per altre frequenze per l'identificazione oggetti o gas es. spettrografia e immagini satellitari
LW: Infrarosso lontano, la banda più comunemente utilizzata adatta alle misure vicine alle temperature ambientali utilizzata in tutte le applicazioni terrestri
XLW: Infrarosso verso microonde: adatta per l'osservazione di temperature inferiori a 250 K, utilizzata per osservazioni astronomiche.

aggiunta del metadato "postproc" nel json del UserComment con i seguenti valori:

TIMEX
ORTOPHOTO
TIMESTACK
TIMEX_COASTLINE
ORTOPHOTO_COASTLINE

pat1 · 2024-01-31T09:41:22Z

Correzioni da apportare alla codifica di UserComment:

Valorizzare se possibile:

camera_tilt
camera_roll

Timerange:

RECSH
- attuale: "timerange": [205, 0, 900]
- da codificare: "timerange": [0, 0, 900]
RECTM
- attuale: "timerange": [205, 0, 900]
- da codificare: "timerange": [0, 0, 900]
T1STK
- attuale: "timerange": [205, 0, 900]
- da codificare: "timerange": [0, 0, 900]
TMXSH
- attuale: "timerange": [205, 0, 900]
- da codificare: "timerange": [0, 0, 900]

Level:

valore attuale: "level": [264, null, null, null]
da codificare: "level":[103,<valore dell'altezza della camera da suolo in millimetri>,null,null]

edigiacomo · 2024-02-13T12:14:16Z

Allego la versione 1.0 delle specifiche Progetto camERa - specifiche EXIF tag v1.0.pdf

pat1 · 2024-04-17T16:57:08Z

Con i file allegati nello zip a:
#277 (comment)
è quindi possibile procedere con i primi test in attesa dei file definitivi

brancomat added the enhancement label Nov 9, 2021

brancomat assigned spanezz Nov 9, 2021

spanezz added a commit that referenced this issue Nov 24, 2021

Cloned NetCDF support as a template for JPEG. Implemented JPEG valida…

4f6cb4d

…tion. refs: #277

spanezz added a commit that referenced this issue Nov 24, 2021

Started implementing the backend for the python JPEG scanner. refs: #277

d8154e0

spanezz added a commit that referenced this issue Nov 24, 2021

Enlarged structure until the python scanning function. refs: #277

8f0d070

spanezz added a commit that referenced this issue Nov 24, 2021

Added initial JPEG scanning, with reftime and area. refs: #277

6a5bf7b

spanezz added a commit that referenced this issue Nov 24, 2021

Updated NEWS.md. refs: #277

a83fa2e

spanezz added a commit that referenced this issue Nov 24, 2021

Merge branch 'master' into issue277. refs: #277

d394e43

spanezz added a commit that referenced this issue Nov 24, 2021

Initial merging of JPEG support. Refs: #277

c5041a4

spanezz assigned dcesari, edigiacomo, pat1 and brancomat Nov 24, 2021

spanezz added the review label Nov 24, 2021

spanezz added a commit that referenced this issue Nov 24, 2021

Added test scanning for the sample given in #277

2412742

spanezz added a commit that referenced this issue Nov 26, 2021

Simplify area for JPEGs. Refs: #277

57f9d44

edigiacomo assigned pat1 and unassigned edigiacomo and spanezz Jun 21, 2023

pat1 assigned edigiacomo and unassigned pat1 Jun 21, 2023

edigiacomo assigned pat1 and unassigned edigiacomo Jun 21, 2023

pat1 assigned edigiacomo and unassigned pat1 Jun 21, 2023

edigiacomo assigned pat1 and unassigned edigiacomo Nov 30, 2023

edigiacomo removed the review label Nov 30, 2023

spanezz self-assigned this Feb 23, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Image file formats support in arkimet #277

Image file formats support in arkimet #277

brancomat commented Nov 9, 2021

pat1 commented Nov 9, 2021

dcesari commented Nov 9, 2021

pat1 commented Nov 9, 2021

spanezz commented Nov 23, 2021 •

edited

Loading

brancomat commented Nov 23, 2021

spanezz commented Nov 23, 2021

spanezz commented Nov 24, 2021

pat1 commented Nov 24, 2021 •

edited

Loading

spanezz commented Nov 25, 2021

dcesari commented Nov 25, 2021

pat1 commented Nov 25, 2021

dcesari commented Nov 26, 2021

spanezz commented Nov 26, 2021

spanezz commented Nov 26, 2021

edigiacomo commented Jun 21, 2023 •

edited

Loading

edigiacomo commented Jun 21, 2023

pat1 commented Jun 21, 2023

edigiacomo commented Jun 21, 2023 •

edited

Loading

pat1 commented Jun 21, 2023

pat1 commented Jun 21, 2023

edigiacomo commented Jun 21, 2023

dcesari commented Jun 21, 2023

edigiacomo commented Jun 21, 2023

edigiacomo commented Nov 30, 2023

edigiacomo commented Jan 23, 2024

pat1 commented Jan 30, 2024

pat1 commented Jan 30, 2024

pat1 commented Jan 31, 2024

pat1 commented Jan 31, 2024

edigiacomo commented Feb 13, 2024

pat1 commented Apr 17, 2024

Image file formats support in arkimet #277

Image file formats support in arkimet #277

Comments

brancomat commented Nov 9, 2021

pat1 commented Nov 9, 2021

dcesari commented Nov 9, 2021

pat1 commented Nov 9, 2021

spanezz commented Nov 23, 2021 • edited Loading

brancomat commented Nov 23, 2021

spanezz commented Nov 23, 2021

spanezz commented Nov 24, 2021

pat1 commented Nov 24, 2021 • edited Loading

spanezz commented Nov 25, 2021

dcesari commented Nov 25, 2021

pat1 commented Nov 25, 2021

dcesari commented Nov 26, 2021

spanezz commented Nov 26, 2021

spanezz commented Nov 26, 2021

edigiacomo commented Jun 21, 2023 • edited Loading

edigiacomo commented Jun 21, 2023

pat1 commented Jun 21, 2023

edigiacomo commented Jun 21, 2023 • edited Loading

pat1 commented Jun 21, 2023

pat1 commented Jun 21, 2023

edigiacomo commented Jun 21, 2023

dcesari commented Jun 21, 2023

edigiacomo commented Jun 21, 2023

edigiacomo commented Nov 30, 2023

edigiacomo commented Jan 23, 2024

pat1 commented Jan 30, 2024

Nomenclatura file riportata qui per comodità

Telecamere

Prodotti

pat1 commented Jan 30, 2024

pat1 commented Jan 31, 2024

pat1 commented Jan 31, 2024

edigiacomo commented Feb 13, 2024

pat1 commented Apr 17, 2024

spanezz commented Nov 23, 2021 •

edited

Loading

pat1 commented Nov 24, 2021 •

edited

Loading

edigiacomo commented Jun 21, 2023 •

edited

Loading

edigiacomo commented Jun 21, 2023 •

edited

Loading