Difference between revisions of "Geodata formats"
Jump to navigation
Jump to search
Wiki-Bitner (talk | contribs) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Placeholder for talking about geodata formats. Please create content. | + | Placeholder for talking about geodata formats. Please create/point to content. |
| + | == Shapefiles == | ||
| + | Shapefiles as they exist today are an open specification published by ESRI. | ||
| + | * [http://en.wikipedia.org/wiki/Shapefile Wikipedia Entry] | ||
| + | * [http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf ESRI Shapefile Specification Whitepaper] | ||
| + | |||
| + | == SDF == | ||
| + | ===Letter from Bob Bray from mailing list (someone please format to wiki)=== | ||
| + | A little clarification on SDF, since it comes up once or twice in this | ||
| + | thread. Jason's earlier descriptions of it's capabilities are pretty good. | ||
| + | It supports multiple Feature Classes / Tables per file, strongly typed | ||
| + | properties, multiple geometry properties per class, with seperate R-Trees | ||
| + | for each geometry property. All of this is stored in a single file that is | ||
| + | heavily optimized for spatial reads. The SDF FDO Provider suppports a | ||
| + | multiple reader / single writer model. The geometries themselves include | ||
| + | simple features + circular arcs in 2D, 2D with Z, 2D with M, or 2D with Z & | ||
| + | M. The R-Trees are currently 2D. | ||
| + | |||
| + | Is it an open format? ABSOLUTELY (we just never wrote a spec, but I am | ||
| + | willing to get it done) | ||
| + | |||
| + | Another little known fact is that in the process of creating SDF we | ||
| + | (Autodesk) literally wrote the code three times. The first time we built SDF | ||
| + | on BerkleyDB, a great open source project but it has some fairly significant | ||
| + | license fees for using it in a proprietary product. The second time we wrote | ||
| + | it on SQLite, however the performance penalaty of the Relational layer was | ||
| + | significant (read orders of magnitude). The third time we chose to strip | ||
| + | away the SQLite relational layer and built directly on the SQLite Backend | ||
| + | components (B-Tree, Pager, and OS Interface). In the end the third | ||
| + | implementation actually turned out to be faster than BDB and is the one we | ||
| + | use today. | ||
| + | |||
| + | All this said, I'd really like to understand everyones requirements for this | ||
| + | new format. If SDF fits thats great, if not thats ok too. We are always | ||
| + | happy to contribute what we can to the community. | ||
| + | |||
| + | Bob | ||
== New Open Geodata Format == | == New Open Geodata Format == | ||
| Line 6: | Line 42: | ||
=== Scope === | === Scope === | ||
* Describe Scope of new format | * Describe Scope of new format | ||
| + | === Willing Developers/Supporters === | ||
| + | * List developers willing to add interfaces to new format or people willing to fund this development | ||
| + | |||
| + | === Preliminary Thoughts === | ||
| + | |||
| + | A dump of my email text to get things started. Please feel free to edit. | ||
| + | |||
| + | The new format -- | ||
| + | |||
| + | * '''Should be fast.''' SQLite is plenty fast, and anything that simply "extends" the Shapefile format to inject relational capabilities should be pretty fast. It should definitely be faster than a geodatabase format (such as PostGIS/ArcSDE) and perhaps even faster than Shapefiles especially while accessing attribute data. DBF is sequential, and searching for textual information is particularly expensive. SQLite has been tuned to excellence. I have been working with it for a few years now, and it really is an amazing product, development community, support, and capabilities. That it is in public domain makes for a transfat-free icing on the cake. | ||
| + | * '''Should be unencumbered by licenses and copyrights.''' Ideally, the new format could also be put back into public domain. We want to remove all encumbrances to encourage rapid and wide adoption. | ||
| + | * '''Should be a single file'''. Well, some like multiple files and some like single files. We can achieve both objectives by using a tar-gzipped packaging such as Apple tends to use for much of its stuff (for example, its Pages wordprocessor uses a tgzipped xml file along with other resources for icons and pictures and stuff). Or, if speed is going to be affected because of gzipping and gunzipping, just a package format (I have no idea if this is a Unix thing or a Mac OS thing -- we, in the Mac world, call them packages... they appear like files in the Finder, and like directories in the shell). | ||
| + | * '''Should be easy to transition to.''' By building the new format on the structure of the Shapefile format, and *in fact*, calling it "open shapefiles" or some such thing, we indicate from its name that the transition is not that revolutionary but is evolutionary. This, hopefully, will bring some name-familiarity, and make the transition less scary. | ||
| + | * '''SQLite's lack of datatypes as an issue''' -- I guess that is a matter of preference. I personally quite like that freedom as it gives me, the application developer, complete control over what goes where. SQLite actually does have now a few datatypes that it respects, but doesn't complain about. Since all users will be accessing the data via an application, as long as the application is well defined, it should be fine. | ||
| + | * SQLite excels at one thing that it has been entrusted to do -- retrieve data that it has been entrusted with at extremely fast speeds, and maintain ACID data integrity in case of a programmatic catastrophe. The transactions themselves are worth their price of admission, which, happily, happens to be zero. | ||
| + | * '''Java support''' -- well, yes, use/work on SQLite JDBC. I have been using it for a few days now and find it to be a pretty competent conduit. Extend it, spatialize it. ANSI standard C is still that magic common denominator that compiles and works predictably on most number of systems. I have a lot against Java, but those who love Java should definitely work on tools for accessing and working with this new format as it would only make the format more widely used and adopted. | ||
| + | * '''Topology''': topology matters. Many vector editing operations are rather impossible without topological information. However, it slows down data access. How to deal with that? | ||
Latest revision as of 21:01, 1 May 2012
Placeholder for talking about geodata formats. Please create/point to content.
Shapefiles
Shapefiles as they exist today are an open specification published by ESRI.
SDF
Letter from Bob Bray from mailing list (someone please format to wiki)
A little clarification on SDF, since it comes up once or twice in this thread. Jason's earlier descriptions of it's capabilities are pretty good. It supports multiple Feature Classes / Tables per file, strongly typed properties, multiple geometry properties per class, with seperate R-Trees for each geometry property. All of this is stored in a single file that is heavily optimized for spatial reads. The SDF FDO Provider suppports a multiple reader / single writer model. The geometries themselves include simple features + circular arcs in 2D, 2D with Z, 2D with M, or 2D with Z & M. The R-Trees are currently 2D.
Is it an open format? ABSOLUTELY (we just never wrote a spec, but I am willing to get it done)
Another little known fact is that in the process of creating SDF we (Autodesk) literally wrote the code three times. The first time we built SDF on BerkleyDB, a great open source project but it has some fairly significant license fees for using it in a proprietary product. The second time we wrote it on SQLite, however the performance penalaty of the Relational layer was significant (read orders of magnitude). The third time we chose to strip away the SQLite relational layer and built directly on the SQLite Backend components (B-Tree, Pager, and OS Interface). In the end the third implementation actually turned out to be faster than BDB and is the one we use today.
All this said, I'd really like to understand everyones requirements for this new format. If SDF fits thats great, if not thats ok too. We are always happy to contribute what we can to the community.
Bob
New Open Geodata Format
Why
Add details of why we need a new format
Scope
- Describe Scope of new format
Willing Developers/Supporters
- List developers willing to add interfaces to new format or people willing to fund this development
Preliminary Thoughts
A dump of my email text to get things started. Please feel free to edit.
The new format --
- Should be fast. SQLite is plenty fast, and anything that simply "extends" the Shapefile format to inject relational capabilities should be pretty fast. It should definitely be faster than a geodatabase format (such as PostGIS/ArcSDE) and perhaps even faster than Shapefiles especially while accessing attribute data. DBF is sequential, and searching for textual information is particularly expensive. SQLite has been tuned to excellence. I have been working with it for a few years now, and it really is an amazing product, development community, support, and capabilities. That it is in public domain makes for a transfat-free icing on the cake.
- Should be unencumbered by licenses and copyrights. Ideally, the new format could also be put back into public domain. We want to remove all encumbrances to encourage rapid and wide adoption.
- Should be a single file. Well, some like multiple files and some like single files. We can achieve both objectives by using a tar-gzipped packaging such as Apple tends to use for much of its stuff (for example, its Pages wordprocessor uses a tgzipped xml file along with other resources for icons and pictures and stuff). Or, if speed is going to be affected because of gzipping and gunzipping, just a package format (I have no idea if this is a Unix thing or a Mac OS thing -- we, in the Mac world, call them packages... they appear like files in the Finder, and like directories in the shell).
- Should be easy to transition to. By building the new format on the structure of the Shapefile format, and *in fact*, calling it "open shapefiles" or some such thing, we indicate from its name that the transition is not that revolutionary but is evolutionary. This, hopefully, will bring some name-familiarity, and make the transition less scary.
- SQLite's lack of datatypes as an issue -- I guess that is a matter of preference. I personally quite like that freedom as it gives me, the application developer, complete control over what goes where. SQLite actually does have now a few datatypes that it respects, but doesn't complain about. Since all users will be accessing the data via an application, as long as the application is well defined, it should be fine.
- SQLite excels at one thing that it has been entrusted to do -- retrieve data that it has been entrusted with at extremely fast speeds, and maintain ACID data integrity in case of a programmatic catastrophe. The transactions themselves are worth their price of admission, which, happily, happens to be zero.
- Java support -- well, yes, use/work on SQLite JDBC. I have been using it for a few days now and find it to be a pretty competent conduit. Extend it, spatialize it. ANSI standard C is still that magic common denominator that compiles and works predictably on most number of systems. I have a lot against Java, but those who love Java should definitely work on tools for accessing and working with this new format as it would only make the format more widely used and adopted.
- Topology: topology matters. Many vector editing operations are rather impossible without topological information. However, it slows down data access. How to deal with that?