Geoserver OilGas: Difference between revisions
From charlesreid1
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Prj2EPSG tool: http://prj2epsg.org/ | Prj2EPSG tool: http://prj2epsg.org/ | ||
=Put the Data on the Server= | |||
Copy the data to a place where Geoserver can see it: | |||
<pre> | |||
cd EIA-Oil-Gas-Maps | |||
sudo cp -r shapefiles /var/lib/tomcat7/webapps/geoserver/data/data/oilgas1 | |||
sudo chown -R tomcat7:tomcat7 /var/lib/tomcat7/webapp/geoserver/data/data/oilgas1 | |||
</pre> | |||
=Make Workspace= | |||
The first step is to create a workspace, which I'll call "oilgas". | |||
Geoserver > Data > Workspaces, and create new workspace | |||
=Make Data Store= | |||
The next step is to create a data store, which is a directory of shape files. I point to the data in the oilgas1 directory. | |||
==Dealing with Projection Issues== | |||
I had some issues with the projection not being found. I ended up opening the .prj projection file (in the same directory as the shapefile), and using http://prj2epsg.org/ to find the corresponding EPSG code. Once I found the code (a four- or five-digit number), I was able to search for it, and find it. This allowed Geoserver to correctly interpret the shapefile data. | |||
Revision as of 14:16, 2 February 2015
This page covers my attempt to get EIA oil and gas lease data into Geoserver.
The data source: https://github.com/talllguy/EIA-Oil-Gas-Maps
Prj2EPSG tool: http://prj2epsg.org/
Put the Data on the Server
Copy the data to a place where Geoserver can see it:
cd EIA-Oil-Gas-Maps sudo cp -r shapefiles /var/lib/tomcat7/webapps/geoserver/data/data/oilgas1 sudo chown -R tomcat7:tomcat7 /var/lib/tomcat7/webapp/geoserver/data/data/oilgas1
Make Workspace
The first step is to create a workspace, which I'll call "oilgas".
Geoserver > Data > Workspaces, and create new workspace
Make Data Store
The next step is to create a data store, which is a directory of shape files. I point to the data in the oilgas1 directory.
Dealing with Projection Issues
I had some issues with the projection not being found. I ended up opening the .prj projection file (in the same directory as the shapefile), and using http://prj2epsg.org/ to find the corresponding EPSG code. Once I found the code (a four- or five-digit number), I was able to search for it, and find it. This allowed Geoserver to correctly interpret the shapefile data.