Add VTATaz data

This commit is contained in:
Will Bradley 2021-02-07 02:34:09 -08:00
parent 13059f15fa
commit 6f28b42e09
10 changed files with 52 additions and 6 deletions

View File

@ -31,6 +31,7 @@ Here are sample screenshots of Sonoma County, Santa Rosa, the City of Sonoma, an
- https://gis-sonomacounty.hub.arcgis.com/datasets/2202c1cd6708441f987ca5552f2d9659 - https://gis-sonomacounty.hub.arcgis.com/datasets/2202c1cd6708441f987ca5552f2d9659
- https://gis-sonomacounty.hub.arcgis.com/datasets/0f5982c3582d4de0b811e68d7f0bff8f - https://gis-sonomacounty.hub.arcgis.com/datasets/0f5982c3582d4de0b811e68d7f0bff8f
- http://download.geofabrik.de/north-america/us/california/norcal-latest.osm.pbf - http://download.geofabrik.de/north-america/us/california/norcal-latest.osm.pbf
- VTATaz: https://drive.google.com/file/d/0B098fXDVjQOhVHBFS0kwcDNGRlU/view
Script: Script:
``` ```
@ -60,26 +61,26 @@ Debian (shp2pgsql is included in postgis)
- For export: sudo apt-get install -y gdal-bin python-lxml - For export: sudo apt-get install -y gdal-bin python-lxml
- ogr2osm https://github.com/pnorman/ogr2osm - ogr2osm https://github.com/pnorman/ogr2osm
- `cd ~`
- `git clone --recursive https://github.com/pnorman/ogr2osm`
- Maybe also/instead: python3-gdal - Maybe also/instead: python3-gdal
- Do NOT install the osgeo package from pip, it's empty and will cause ogr import errors. - Do NOT install the osgeo package from pip, it's empty and will cause ogr import errors.
## Running ## Running
- First, prepare Postgres for an OSM schema that'll be used for the output data, by running this SQL in your desired database: https://github.com/openstreetmap/osmosis/blob/master/package/script/pgsnapshot_schema_0.6.sql - We are assuming that the county data uses a WGS84 aka EPSG:4326 geographical projection, which was true as of last check and is also what OSM uses.
- Run the following SQL as a superuser (postgres) inside the `openstreetmap` database to enable the PostGIS and hstore extensions: `CREATE EXTENSION postgis; CREATE EXTENSION hstore;`
- Unzip the `original_data` and open a shell in that folder.
- Here we are assuming that the county data uses a WGS84 aka EPSG:4326 geographical projection, which was true as of last check and is also what OSM uses.
- Run from your shell: `shp2pgsql -s 4326 -I Parcels__Public_.shp | psql -d openstreetmap -U openstreetmap -W` - Run from your shell: `shp2pgsql -s 4326 -I Parcels__Public_.shp | psql -d openstreetmap -U openstreetmap -W`
- `shp2pgsql -s 4326 -I Sonoma_County_Building_Outlines.shp | psql -d openstreetmap -U openstreetmap -W` - `shp2pgsql -s 4326 -I Sonoma_County_Building_Outlines.shp | psql -d openstreetmap -U openstreetmap -W`
- `shp2pgsql -s 4326 -I osm-buildings-01-03.shp | psql -d openstreetmap -U openstreetmap -W` - `shp2pgsql -s 4326 -I osm-buildings-01-03.shp | psql -d openstreetmap -U openstreetmap -W`
- `osm2pgsql -d openstreetmap -c --prefix son --slim --extra-attributes --hstore --latlong norcal-latest.osm.pbf -U openstreetmap -W -H localhost -P 5432` - `osm2pgsql -d openstreetmap -c --prefix son --slim --extra-attributes --hstore --latlong norcal-latest.osm.pbf -U openstreetmap -W -H localhost -P 5432`
Now all the data is in Postgres. For processing and conflation, read through and execute `conflation.sql` as per your comfort level.
osm2pgsql should create tables like `son_polygon` for later. osm2pgsql should create tables like `son_polygon` for later.
Now all the data is in Postgres. For processing and conflation, read through and execute `conflation.sql` as per your comfort level.
## Exporting and uploading ## Exporting and uploading
TODO, Osmium TODO, `trial.sh`
## Import and validation ## Import and validation

BIN
original_data/VTATaz/VTATaz.dbf Executable file

Binary file not shown.

View File

@ -0,0 +1 @@
PROJCS["NAD_1983_StatePlane_California_III_FIPS_0403_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",6561666.666666666],PARAMETER["False_Northing",1640416.666666667],PARAMETER["Central_Meridian",-120.5],PARAMETER["Standard_Parallel_1",37.06666666666667],PARAMETER["Standard_Parallel_2",38.43333333333333],PARAMETER["Latitude_Of_Origin",36.5],UNIT["Foot_US",0.3048006096012192]]

BIN
original_data/VTATaz/VTATaz.sbn Executable file

Binary file not shown.

BIN
original_data/VTATaz/VTATaz.sbx Executable file

Binary file not shown.

BIN
original_data/VTATaz/VTATaz.shp Executable file

Binary file not shown.

View File

@ -0,0 +1,2 @@
<?xml version="1.0" encoding="UTF-8"?>
<metadata xml:lang="en"><Esri><CreaDate>20150317</CreaDate><CreaTime>10502500</CreaTime><ArcGISFormat>1.0</ArcGISFormat><SyncOnce>TRUE</SyncOnce><DataProperties><lineage><Process ToolSource="c:\program files (x86)\arcgis\desktop10.1\ArcToolbox\Toolboxes\Data Management Tools.tbx\CalculateField" Date="20150317" Time="105025">CalculateField VTATaz Area [Area] VB #</Process></lineage></DataProperties></Esri></metadata>

BIN
original_data/VTATaz/VTATaz.shx Executable file

Binary file not shown.

42
original_data/VTATaz/VTATaz.vpr Executable file
View File

@ -0,0 +1,42 @@
[TPPLUS]
PROJECT=NETWORK
[VTATaz.shp]
Visible=1
LayerType=5
LayerSubType=0
DefaultCentroidColor=8421504,0,0
DefaultNodeColor=65280,0,0
DefaultCentroidLinkColor=8421504,0,1
DefaultLinkColor=65280,0,1
BaseX=0
BaseY=0
ScaleX=0
ScaleY=1
LayerMinScale=0
LayerMaxScale=0
LinkPostMinScale=0
LinkPostMaxScale=0
NodePostMinScale=0
NodePostMaxScale=0
BoundingBox=5696745.29818872,1381585.77339379,6646530.42427279,2507172.37079333
ExternalDBF=
ExternalLinkage=
ActiveNodeSelectGroup=0
NodeSelectGroup1=
NodeSelect1=
ActiveNodeColorGroup=0
NodeColorGroup1=
NodeColorPaletteIndex1=0
NodeDrawOffset1=0
ActiveLinkSelectGroup=0
LinkSelectGroup1=
LinkSelect1=
ActiveLinkColorGroup=0
LinkColorGroup1=
LinkColorPaletteIndex1=0
LinkDrawOffset1=0
ActiveSelectGroup=0
SelectGroup1=
Select1=

BIN
original_data/VTATaz/VTAtaz.mxd Executable file

Binary file not shown.