Back in the dim and distant past, these formats came about from different proprietary software developers. GRID came from ESRI. IMG came from ERDAS and TIFF came from Aldus (are they still on the go?). So that explains why we have the three of them. There are some differences though:
Portability - of the three you mention the GeoTiff is probably the most ...
Shapefiles are the lowest common denominator of GIS vector data file exchange: send an archive of shapefiles, and you can pretty much guarantee that someone will be able to build a basic GIS from it.
SpatiaLite's advantages include:
everything's in one file; none of the shp/shx/dbf/idx/prj per layer mess.
logic as well as data can be included, in the form ...
The idea you're probably thinking of is GeoPackage.
The background to the requirement came from the US Army Geospatial Center which is part of the Corps of Engineers, who were looking for a way to put maps and other information (points or interest, routes, photographs and other observations) into a simple "one file has it all" format for mobile ...
I would suggest downloading and installing QGIS. You can then open the file that you link to and export the data in variety of formats.
The most common format for spatial data of this type is a shapefile which is one of the files that you linked to (TM_WORLD_BORDERS_SIMPL-0.2.zip). The reason that it is a zipfile is that there are several associated files ...
Shapefiles are bound to one type of geometry, so you get a bunch of files for a single project. The field names are restricted too due to using an antiquarian database format.
In spatialite, you can hold the whole project data in one file; and name the fields how you want (well, almost).
The only disadvantage of spatialite is the fast update cycle, making ...
In the Esri world an .asc file usually refers to the output created by the GRIDASCII command (ArcInfo Workstation) or Raster to ASCII tool (ArcGIS for Desktop). In practice it can mean just about any format, usually plain text, meaning one can't assume from the .asc extension what it looks like inside.
It's an interchange format, meaning it's not (normally) ...
Well, where to start.
Although you can divide data by vector/raster etc there are some obvious problems.
For example an Oracle database can store vector or raster (as can other databases).
I work at Safe Software where we generally prefer to look at Spatial data (rather than just GIS) and so divide into different categories according to use.
You're almost there. This is on Windows 7, Python 2.6.5 32bit, and GDAL 1.9.0:
>>> from osgeo import ogr
>>> driver = ogr.GetDriverByName("FileGDB")
>>> ds = driver.Open(r"C:\temp\buildings.gdb", 0)
<osgeo.ogr.DataSource; proxy of <Swig Object of type 'OGRDataSourceShadow *' at 0x02BB7038> >
The definitive reference on the shapefile format is the ESRI Shapefile Technical Description.
It is misleading to describe the shx as being an "index." Instead, it is the direct access offset file. There is no data in the shx, only a clone of the first hundred bytes and record number and offset to the starting byte of that record in the shp. The only ...
In addition to scruss' answer, shapefiles has some limitations:
max field name length is 10 characters
maximum file size (.dbf / .shp) is 2GB
numeric attributes are stored as characters (integers/floats), causing potential problems with rounding etc
NULL values are interpreted differently between systems
Shapefile (ESRI) Tech Spec PDF 2.5 billion files est
MapInfo Tab/MIF (Pitney Bowes Business Insight) Tech Spec 1.5 billion files est
AutoCAD DWG (AutoDesk)** has 18 major variants of the DWG
"Autodesk estimates that in 1998 there were in excess of two billion DWG files in existence"
Fastest adopted format is KML/KMZ Google Earth/Pro est 0.5 ...
One reason is because spaces carry special meaning in several programming/scripting languages.
Making a habit of naming files and folders with underscores is a good practice because then the " " (spaces) will not be treated as a new-line by some languages.
Example - A folder called "GIS Data" is a bad folder name.
This is because if I try to access it with ...
Short answer: I suspect there is no such standard for TIFF or GeoTIFF overviews. There are multiple implementations, methods and formats to define overviews for GeoTIFFs.
GeoTIFF is based on the TIFF format (PDF specification for Revision 6.0, from 1992). The format has support for multi-page documents or subfiles, similar to a multi-page PDF.
A GeoTIFF ...
Shx certainly has nothing to show on a map alone as you can read from the specification https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf.
You are indeed right in that it is possible to open shapefile by selecting the .shx part with QGIS 3.0.3 but I can't see any difference on the location. I believe that shapefile is still opened through the same ...
File extensions are mostly meaningless. Sure, they might indicate the file's format but you can easily rename a .exe file to .txt and the file would not change itself. File extensions are mostly used for ease of usage and on some operating systems to decide what to do (which program to launch) if a user tries to "open" a file. Opening an .exe file that was ...
Shapefile format doesn't allow multiple geometry types, so you should use another format, like GeoJSON. See also OGR merge shapefiles of different geom type into a single GeoJSON feature collection, How to Merge/Join GeoJSON and JSON? and https://gist.github.com/migurski/3759608
GDAL supports .img format, both the basic Imagine and the extended Imagine (greater than 2GB), thus any software that utilizes GDAL drivers would support ERDAS Imagine.
The most workable and well documented that I have seen is QGIS. It is also open source and therefore free.
No it's not possible.
Like PolyGeo said you could write a conversion script using ArcPy that reads the QGIS project file (which is just XML) and load each layer. There would be a bit of work but you might even be able to match some of the styling. However there would be a lot of effort in this and it might not be worth it for a single project.
GDAL's ENVI driver can be used to write headerless binary data files. The default data interleave is band sequential (BSQ), but BIP or BIL interleave options can be specified as a creation option.
For example, to convert a GeoTIFF file foo.tif to a headerless file foo.bin:
gdal_translate -of ENVI foo.tif foo.bin
The ASCII file foo.bin.hdr will also be ...
QGIS has become much more robust for the conversion between kml and shp. Just use the Save As from the right click menu on the layer. Or open up each of those file types from the Add New Layer menu, be sure to change the file type in the dialog box.
I like @celenius' answer; however, another option would be to export the the World Borders Dataset to CSV using ogr2ogr. I just downloaded your preferred dataset and ran this command with ogr2ogr --note that your script should be a single string without any line breaks. I find them easiest to write in notepad with wordwrap turned on, then I copy them into my ...
The easiest format for external reading/writing would be a pure binary file (BSQ, BIL, or BIP). These have absolutely no header information contained within--only a stream of bits beginning with the first data point and ending with the last data point. The ordering of bits in n dimensions will vary on the interleave method: either band sequential (BSQ), band ...
If your question is simply about viewing the S57 files (extension .000), then you will be happy that GDAL supports that format for reading files. As a result any software using GDAL, like Qgis, can open S57 files. See here for documentation on the S-57 ENC file format.
Also see here for a very nice Opensource navigation software.
If you want to write to ...
There is no universal vector format in GIS.
However, some formats are proprietary and other are openly specified (like the shapefile) so that they can be read and/or written by other softwares (if they decide to implement).
For data sharing, the best solution to date is to use shapefile, which is now the most widespread format. Shapefile is however an old ...
Have you tried running the Compact tool on your file geodatabase? Compacting could get your geodatabase size down. I would not recommend deleting any of the files in the file geodatabase structure, as you are likely to kill it doing that. You say the "default" file geodatabase...personally I try to not keep anything in there that is of any importance and ...
E00 is a proprietary ESRI file format intended to support the transfer between ESRI systems of different types of geospatial data used in ESRI software ( Old systems anyway, people use the ESRI file geodatabase now ). Usually, people then convert to coverages and work with those, they don't use the E00 file directly (somebody correct me if I'm wrong).