[GRASS-user] Re: Projection of latlong sites file doesn't work

[Joel Pitt]

In addendum, I realised that I had the latitude and longitude reversed
when importing the ascii file. Silly mistake!

-Joel

On 7/25/06, Joel Pitt <joel.pitt at gmail.com> wrote:
> I have a file in the following format:
>
> -45.075000,170.975000,80.173343
> -45.025000,170.975000,72.205741
> ...
> -44.975000,170.975000,93.254147
>
> i.e. latitude, longitude, and an attribute in the third column.
>
> I import it into a latlong location using v.in.ascii and then try and
> project it into a location that uses the New Zealand Mapping Grid
> projection, but I get the following output:
>
> ------------
> > v.proj input=lhumile_ddays location=latlong
>
> Input Projection Parameters: +proj=latlong +a=6378388 +rf=297 +no_defs
> +towgs84=59.47,-5.04,187.44,0.47,-0.1,1.024,-4.5993
> Input Unit Factor: 1
>
> Output Projection Parameters: +proj=nzmg +lat_0=-41.0000000000
> +lon_0=173.0000000000 +x_0=2510000.0000000000 +y_0=6023150.0000000000
> +a=6378388 +rf=297 +no_defs
> +towgs84=59.47,-5.04,187.44,0.47,-0.1,1.024,-4.5993
> Output Unit Factor: 1
>
> Creating vector file...
> pj_transform() failed
> cause: latitude or longitude exceeded limits
> Error in pj_do_transform
>
> ------------
>
> None of the latitude/longitude values appear to be out of range. Is
> there anyway to get more information? Or does anyone else have a clue
> on how to fix this?
>
> Thanks for your time.
>
> --
> -Joel
>
> "Wish not to seem, but to be, the best."
>                 -- Aeschylus
>


-- 
-Joel

"Wish not to seem, but to be, the best."
                -- Aeschylus