Nice work Allan - any idea what 2GB would get you - all addresses for US?, for a state?
Alex, I'm investigating another couple of options. One is to the use the Datadirect ODBC XML driver to connect to the file geodatabase: this would kill off that limitation. The other option is FDO from OSGEO.
To give you an idea of what's possible with this method: The OpenFlights.org data in Great Circles produced a 1.89 GB point shapefile. 13,000,000 rows. What you see above is a 60,000 row table.
Message was edited by: Allan Walker: added link to OpenFlights in Tableau TDE
Any more detail on what happens in these steps?
- RIght click on your personal geodatabase and create a table.
- You'll be using the Microsoft Jet Engine to connect to this: you may have noticed that the file extension of the personal geodatabase is .mdb
You showed a point file, so I am guessing you imported a plain text file with lat/long fields or something like that? OR maybe it was the attribute file from a shp file? I am just a bit curious what goes on in these two steps.
Oh man this is cool. Anything about this process that wouldn't work in QGIS?
Once I "crack" the ESRI file database (it's either the API or the XML), then we can import/connect to QGIS.
QGIS can be a bit flaky though, and the code changes a lot. I might be able to crack the EVIS ODBC plug in, so there is hope.
Allan Walker wrote:
This opens up a whole new world. You can now easily create custom boundaries, geocode addresses, create lines from X/Y (rhumb, great circles)...what ever you need to do in ESRI. The only limitation is 2GB file size.
i can see use for point-file use, like the example of the airports. How about the other ones (custom boundaries, create lines from X/Y etc...
could you please shown an example (or workbook) for them just like the airports example for point-files ?
For Polygon SHP -
- If not already done, add XY from geoprocessing toolbox
- Export SHP (FeatureClass to FeatureClass) to single geodatabase (personal mdb, not file geodatabase)
- Connect via Access to the mdb, you'll see the table names.
I'm working on the GADM.org Shapefile right now, I want to show how much we can push this method.
Here's (part) of the GADM set, dynamically linked to ESRI.
Afghanistan & Argentina boundaries in Tableau:
- In ESRI, pull the SHP file over to layers.
- In ESRI, use ET Wizard to do polygon to point, vertices only, save as Featureclass into your personal GDB (mdb)
- In Tableau, connect to the mdb using Access, point to the new Featureclass you created table (WORKBOOK HERE)
- In Tableau, make ET_X AVG and ET_Y AVG Continuous dimensions.
- Use polygon mark type
- Path = ET_Order
- LOD = ET_ID
You can now have boundary level detail in Tableau. I'm off to strip the SHP table down, to see if the Global GADM will fit inside the 2GB limit.
For QGIS, export your shapefiles to an instance of PostGIS in PostgreSQL, which I did to get the OpenStreetMap.osm shapefiles in. You could then either serve up the PostGIS tables in Geoserver, or connect to the shapes using a PostgreSQL connection inside Tableau.
This may be old...
So I've got a full blown ESRI environment and some tableau folks want my
Company District Boundaries to be imported in tableau... POLYGON featureclass
I tried giving them Personal Geodatabase - told them to connect using access
but this does not work.
has there been any progress from tableau on this???
You need to convert your ESRI Shapefile polygon class to "Tableau ready" polygon format, i.e. give them a point order.
To enable this in ESRI, use ET Wizards "Polygon to Point" tool. It will generate more columns - "ET_Order", "ET_ID", "ET_X" and "ET_Y". X on columns, Y on rows, ET_ID on level of detail, ET_Order on path shelves. You can use the same connection method as before.