Glynn wrote:
> The SW fragment of NH which is in zone 18 is only around half a
> degree; projecting that into zone 19 isn't really an issue.
> Or you could just use a custom transverse Mercator projection
> with the central meridian at e.g. 71d30'W.
... and of course there will be a state plane pr
Is projecting to NH state plane and option? Along the lines of using
something more localized.
Mark
On May 14, 2010, at 2:06 PM, Kurt Springs wrote:
Thanks Rich and Dylan
I downloaded the pdf of document #1395. At the moment I am leaning
toward Lambert Conic Conformal (1SP) since it see
For the record:
not only norway has compensation zones in the UTM grid (so to stay in just one
fuse) but also here in italy we have some regions (LAU2 units) that span across
32 and 33 and project all on 32.
As far as you don't exceed 2/300 km, IMHO you can extend into the adjacent
fuse...
HTH
On Fri, May 14, 2010 at 5:05 AM, Kurt Springs wrote:
> Hi Folks,
>
> I have been playing with the seamless maps from the USGS. Specifically, my
> question is on the effect of Latitude/Longitude vs UTM with respect to
> hydrology modules such as r.watershed and r.topidx. I was trying to generat
Dylan Beaudette wrote:
> > There is a USGS technical report from the mid-1980s that's the standard on
> > projections. While it is becoming more rare to locatate, see if you can find
> > a copy.
>
> I think that Rich is referring to this USGS document, #1395
>
> http://pubs.er.usgs.gov/usgspub
Thanks Rich and Dylan
I downloaded the pdf of document #1395. At the moment I am leaning toward
Lambert Conic Conformal (1SP) since it seems to use Lat/Long of Natural Origin,
in case I need to use a GPS. If I am reading you right Latitude and longitude
don't even come into the equation, jus
Jonathan Greenberg wrote:
> I have some rasters in a grass data directory on a different mounted
> drive in unix that i want to copy into a different data directory +
> mapset -- i can't seem to figure out how to do this with g.copy, which
> AFAIK only copies from mapsets within a given data dire
Hi Micha,
I tried your suggestion after setting the region to 20m instead of the
raster DEM's 25m.:
v.surf.rst input="dem_2628cc_...@c83" layer=0
elev="dem_2628cc_rst_elev" tension=40. segmax=40 npmin=120
dmin=9.998022 dmax=49.990111 zm ult=1.0
This worked, but the differences between the raste
On Fri, May 14, 2010 at 6:22 AM, Rich Shepard wrote:
> On Thu, 13 May 2010, Kurt Springs wrote:
>
>> This was interesting in that it told me that r.topidx could not be run
>> with latitude and longitude and I had to convert to UTM. I was wondering
>> if this is the answer to the problem and I just
On Thu, 13 May 2010, Kurt Springs wrote:
This was interesting in that it told me that r.topidx could not be run
with latitude and longitude and I had to convert to UTM. I was wondering
if this is the answer to the problem and I just had to convert to UTM.
Kurt,
Lat/Long represents geographi
2010/5/14 subbu sravan :
>
> Can any body help me to classify an image in GRASS 6.4.0
> If you send an Video, I will be very thankful to you
http://grass.osgeo.org/wiki/Image_classification
Martin
--
Martin Landa * http://gama.fsv.cvut.cz/~landa
___
Can any body help me to classify an image in GRASS 6.4.0
If you send an Video, I will be very thankful to you
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Hi Jamie,
Thanks, this worked perfectly.
Regards
Hanlie
2010/5/13, Jamie Adams :
> Did you adjust the region also? To do this properly, you need to first scan
> the file using r.in.xyz to get the extents. I'd also use the shell style
> output.
>
> r.in.xyz -sg input="2628cc.ORT.xyz" output="de
13 matches
Mail list logo