I work extensively in the state of Delaware and the mapping information that they provide is based on ESRI ID 102257 with an ESRI WKT Name of NAD_1983_HARN_StatePlane_Delaware_FIPS_0700. As a new user of GRASS, what would be the best way to import that data? Ultimately, I wish to reproject state plane meters to state plane feet then use those files to import into a MODFLOW project. Perform the modeling, then export that information back to GRASS for additional processing.
Just starting to use GRASS myself, so this certainly isn't an expert
opinion. You can reproject the data using ogr2ogr without having to
bring it into GRASS at all.
The best resource I have found so far for GRASS is the book by Neteler
and Mitasova, "Open Source GIS, a GRASS GIS Approach". It's not
cheap, but it seems to cover all the issues you are going to
encounter, including this one. It recommends that to import the data,
you should create a new location with the GUI and use the data set to
define the extents, then import the data using the v.in.ogr tool.
Apologies if that's old news to you, it's still relatively new to me.
Roger
--
On Fri, Oct 16, 2009 at 9:15 AM, Bob Byer <hydrogeo_1@yahoo.com> wrote:
All,
I work extensively in the state of Delaware and the mapping information that
they provide is based on ESRI ID 102257 with an ESRI WKT Name of
NAD_1983_HARN_StatePlane_Delaware_FIPS_0700. As a new user of GRASS, what
would be the best way to import that data? Ultimately, I wish to reproject
state plane meters to state plane feet then use those files to import into a
MODFLOW project. Perform the modeling, then export that information back to
GRASS for additional processing.
Just starting to use GRASS myself, so this certainly isn’t an expert
opinion. You can reproject the data using ogr2ogr without having to
bring it into GRASS at all.
The best resource I have found so far for GRASS is the book by Neteler
and Mitasova, “Open Source GIS, a GRASS GIS Approach”. It’s not
cheap, but it seems to cover all the issues you are going to
encounter, including this one. It recommends that to import the data,
you should create a new location with the GUI and use the data set to
define the extents, then import the data using the v.in.ogr tool.
Apologies if that’s old news to you, it’s still relatively new to me.
I work extensively in the state of Delaware and the mapping information that
they provide is based on ESRI ID 102257 with an ESRI WKT Name of
NAD_1983_HARN_StatePlane_Delaware_FIPS_0700. As a new user of GRASS, what
would be the best way to import that data? Ultimately, I wish to reproject
state plane meters to state plane feet then use those files to import into a
MODFLOW project. Perform the modeling, then export that information back to
GRASS for additional processing.
All,
I work extensively in the state of Delaware and the mapping information that they provide is based on ESRI ID 102257 with an ESRI WKT Name of NAD_1983_HARN_StatePlane_Delaware_FIPS_0700. As a new user of GRASS, what would be the best way to import that data? Ultimately, I wish to reproject state plane meters to state plane feet then use those files to import into a MODFLOW project. Perform the modeling, then export that information back to GRASS for additional processing.
I see in the EPSG database that NAD_1983_HARN for Delaware with units of feet is EPSG code 2880:
# NAD83(HARN) / Delaware (ftUS)
<2880> +proj=tmerc +lat_0=38 +lon_0=-75.41666666666667 +k=0.999995 +x_0=200000.0001016002 +y_0=0 +ellps=GRS80 +to_meter=0.3048006096012192 +no_defs
Does that exactly match ESRI's 102257?
And the EPSG code for for the CRS with meter units is 2776, as listed at the bottom of your website..
So if you create two locations, one based on each of the EPSG codes, you can then import your data (into the correct location), and reproject to the other location to get units in meters.
All,
I work extensively in the state of Delaware and the mapping information that they provide is based on ESRI ID 102257 with an ESRI WKT Name of NAD_1983_HARN_StatePlane_Delaware_FIPS_0700. As a new user of GRASS, what would be the best way to import that data? Ultimately, I wish to reproject state plane meters to state plane feet then use those files to import into a MODFLOW project. Perform the modeling, then export that information back to GRASS for additional processing.
I see in the EPSG database that NAD_1983_HARN for Delaware with units of feet is EPSG code 2880:
NAD83(HARN) / Delaware (ftUS)
<2880> +proj=tmerc +lat_0=38 +lon_0=-75.41666666666667 +k=0.999995 +x_0=200000.0001016002 +y_0=0 +ellps=GRS80 +to_meter=0.3048006096012192 +no_defs
Does that exactly match ESRI’s 102257?
And the EPSG code for for the CRS with meter units is 2776, as listed at the bottom of your website…
So if you create two locations, one based on each of the EPSG codes, you can then import your data (into the correct location), and reproject to the other location to get units in meters.
> I work extensively in the state of Delaware and
> the mapping information that they provide is based on ESRI
> ID 102257 with an ESRI WKT Name of
> NAD_1983_HARN_StatePlane_Delaware_FIPS_0700. As a new
> user of GRASS, what would be the best way to import that
> data?
create a new location using the text based setup program.
The text and Tcl/Tk based startups lead you to that. (this
starts the g.setproj module)
You will then be prompted to enter NAD83, state, county FIPS
code, and which units you want to use.
Support for this has not yet been added to the wxGUI startup
wizard.
import data with r.in.gdal and v.in.ogr (and others).
Ultimately, I wish to reproject state plane
meters to state plane feet
create a second location with the other units, then pull
imported data into the target location with r.proj and v.proj.
if using the EPSG method double check all PROJ.4 terms match.
I notice that GDAL ships with /usr/share/gdal15/stateplane.csv.
Also /usr/share/gdal15/esri_extra.wkt which lists your ESRI ID
number. /usr/share/proj/esri and esri.extra also have it.