User Tools

Site Tools


lovergine:data_format_policy

This is an old revision of the document!


Data Format Policy

In order to ensure interoperability for all different platforms and operating systems used by partners, we introduced strict guidelines about formats to be used for both data and documents.

Geodata formats policy

All formats used to exchange geo data of any kinds among partners must be INSPIRE compliant and based on OGC (Open GIS Consortium) recommendations, in order to ensure easy interoperability, even when different programs are used. Also, keep in mind that target sites are localized in various areas of the globe, so a global coordinate reference system should be preferred.

Raster data

  • Preferred format (up to 4GB): multiband/multifile GeoTiff
  • Reference ellipsoid/datum: WGS84
  • Reference plane projection: UTM (zone depends on area considered → to be detailed later)
  • Optional Color table: 24 bits (note that only 8 bit LUTs per band are supported by *all* programs)
  • Always provide a companion world file (.TFW) to allow at least a rough localization for people who do not use GIS tools

Useful hints

  • Use NULL/ALPHA whenever reasonable/useful
  • You have to adopt a suitable tiling for big grids (> 4.GB) and possibly provide a vector skeleton of the tiles boundings in geo coordinates
  • Avoid as much as possible proprietary formats (e.g. ECW, Kakadu, MrSid, etc.)
  • Eventually ask for advice before providing/ordering data

Vector data

  • Vector formats: shapefile and/or KML
  • Reference ellipsoid/datum: WGS84
  • Reference plane projection: UTM (zone depends on area considered → to be detailed later)
  • Provide an OGC WKT (or .PRJ) companion file.
  • Avoid non ANSI 7bits ASCII encoding for alphanumeric data, or use UTF8 just in case.

Document formats policy

lovergine/data_format_policy.1291285959.txt.gz · Last modified: 2010/12/02 11:32 by frankie