|
I linked to the gdb. The pickup table has 14522207 records in it. Copying and pasting that table as a local table in the project fails, I suppose because there are either duplicates or NULLs in the field used as a btree index. That's easy to deal with using a simple query to first build a new, local table: INSERT INTO [pickup] ([OBJECTID], [Shape], [vendor_id], [pickup_dat], [dropoff_da], [passenger_], [trip_dista], [pickup_lon], [pickup_lat], [rate_code], [store_and_], [dropoff_lo], [dropoff_la], [payment_ty], [fare_amoun], [surcharge], [mta_tax], [tip_amount], [tolls_amou], [total_amou], [do_geometr], [tzone]) SELECT [OBJECTID], [Shape], [vendor_id], [pickup_dat], [dropoff_da], [passenger_], [trip_dista], [pickup_lon], [pickup_lat], [rate_code], [store_and_], [dropoff_lo], [dropoff_la], [payment_ty], [fare_amoun], [surcharge], [mta_tax], [tip_amount], [tolls_amou], [total_amou], [do_geometr], [tzone] FROM [taxi.gdb]::[pickup] You can then add an index to it, say, on the mfd_id field. The zones table and drawing are small and easily copy/paste from the linked gdb into the local project. As you can see from the field names in the query above, the gdb in the zipfile does not match the SQL in the blog post: field names are different. so the query has to be re-written slightly. That might indicate version skew in what currently is in the zip file as compared to what is described in the blog. Next, the query needs to be edited slightly to work with field names as they are in the gdb that is in the zip file. I haven't had time to do that today, but perhaps tomorrow.
|