[please keep it in the list]
On Thu, Jun 21, 2018 at 9:12 AM, Paul Shapley wrote:
>
> Thank you Markus...here are the results of g.region -p and r.info
>
> g.region -p
> projection: 99 (OSGB 1936 / British National Grid)
> zone: 0
> datum: osgb36
> ellipsoid: airy
> north:
I have tried to run i.i.nightlights.intercalibration on the command line
and got the following error:
What could be happening?
Thanks a lot
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
I have tried to run i.i.nightlights.intercalibration on the command line
and got the following error:
What could be happening?
Thanks a lot
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
Hello all
I'm trying to create some images with m.nviz.image, but all I get as output
is a 11 byte ppm...
Some of the options are quite puzzling in terms of mixing units:
position=x,y
Viewpoint position (x,y model coordinates)
height=value
Viewpoint height (in map units)
focus=x,y,z
Focus to
Hi Gabriel,
Are you using Windows? I think you cannot use g.list inside a command as we
do in Linux. Solution would be to first get the list of comma separated map
names and then paste it in the i.nightlights command.
HTH,
Vero
El jue., 21 jun. 2018 11:05, Gabriel Cotlier escribió:
> I have
Hi Rich,
Looks like I confused things a bit.
ESRI ArcINFO used two formats that spreded files into a directory with the
layer name and another directory called INFO. In the directory with the
layer name, the files had the .ADF extension you mentioned in the first
email. But their content is
On Thu, 21 Jun 2018, Daniel Victoria wrote:
ESRI ArcINFO used two formats that spreded files into a directory with the
layer name and another directory called INFO. In the directory with the
layer name, the files had the .ADF extension you mentioned in the first
email. But their content is
OK.
I tried to download the data you placed on file dropper (other email
tread). But both links you sent gave me corrupt files.
If you can manage to place the files in some shared folder or point to the
original data source, I can take a look.
Have you tried opening in some other software, like
Hi Marcus,
Thanks again for your patience with this issue. It seems that whatever i
set in the memory of 'i.segment' to it throws up the same 'G_malloc' error
with the same 3 gb shortfall. I had another idea which is to make a smaller
subset image (but if i do this) will the new subset of 'id'
Hello Vero,
Thanks a lot for your response.
I have tried that with no results, with the error in the image bellow:
On Thu, Jun 21, 2018 at 12:12 PM, Veronica Andreo
wrote:
> Hi Gabriel,
>
> Are you using Windows? I think you cannot use g.list inside a command as
> we do in Linux.
Hi Paul,
On 21/06/18 16:54, Paul Shapley wrote:
Hi Marcus,
Thanks again for your patience with this issue. It seems that whatever i
set in the memory of 'i.segment' to it throws up the same 'G_malloc'
error with the same 3 gb shortfall. I had another idea which is to make
a smaller subset
It is a bit difficult to read, can you post the command you used? It seems
you typed image twice, suffic instead of suffix and you are using $() to
pass the list of map names which is not necesary, AFAIU. Try the following:
i.nightlights.intercalibration image=img1,img2,img3 suffix=c
On Thu, 21 Jun 2018, Daniel Victoria wrote:
I tried to download the data you placed on file dropper (other email
tread). But both links you sent gave me corrupt files.
Daniel,
There was something funky going on with file dropper. But, I just
successfully uploaded bare_earth.tar.xz there:
On Thu, 21 Jun 2018, Daniel Victoria wrote:
Daniel,
What I've seen is that most of you data has values -3.4028e+38 which
appears to be the NODATA value. So, are you sure this part of the data is
not a corner of the mapped area? Because there is valid data for the upper
and left borders. Also,
On Thu, 21 Jun 2018, Helmut Kudrnovsky wrote:
as already mentioned in another mail, the easiest thing to stay updated
about svn activities is to look at:
https://lists.osgeo.org/pipermail/grass-commit/
Helmut,
This morning I checked out the trunk, configured and built it. This told
me the
Rich,
I was able to open your GRID in QGis. And if it works in QGis, it should
work in GRASS too.
What I've seen is that most of you data has values -3.4028e+38 which
appears to be the NODATA value. So, are you sure this part of the data is
not a corner of the mapped area? Because there is valid
Trying to help those trying to help Rich:
the tiling scheme is available in a web viewer here:
https://gis.dogami.oregon.gov/maps/lidarviewer/
the archive containing the data in question is available here:
http://www.oregongeology.org/pubs/ldq/LDQ-45122C3.zip (1.8 GB)
you need to patch
On Thu, 21 Jun 2018, Markus Neteler wrote:
As of now, i.e. date -u
Thu Jun 21 20:49:37 UTC 2018
... the SVN trunk revision is 72867.
Markus,
Then I wonder what changed here:
$ date -u
Thu Jun 21 21:23:28 UTC 2018
$ svn up
Updating '.':
At revision 72869.
Any thoughts?
Best regards,
Rich Shepard wrote
> On Thu, 21 Jun 2018, Markus Neteler wrote:
>
>> As of now, i.e. date -u
>> Thu Jun 21 20:49:37 UTC 2018
>>
>> ... the SVN trunk revision is 72867.
>
> Markus,
>
>Then I wonder what changed here:
>
> $ date -u
> Thu Jun 21 21:23:28 UTC 2018
>
> $ svn up
> Updating '.':
On Thu, Jun 21, 2018 at 7:24 PM, Rich Shepard
wrote:
>
> My problems are that pointing r.in.gdal to the hdr.adf files display
only
> the strange wedge/rectangle I attached to messages earlier in this thread.
> They should be retangles for a full 1 degree x 1 degree topographic quad
map
> with
On Thu, 21 Jun 2018, Markus Metz wrote:
you need to patch together all bare earth coverages from all years in
order to get a more complete coverage
Markus,
I missed this point when I read the descriptive data. It certainly
explains why there's 2009_OLC_Hood-to-Coast, 2013_OLC_Clackamol,
On Thu, 21 Jun 2018, Rich Shepard wrote:
to replacing this ancient 32-bit system with a more capable 74-bit system.
Er, ... that should be 64-bit system.
Rich
___
grass-user mailing list
grass-user@lists.osgeo.org
Rich,
On Wed, Jun 20, 2018 at 11:41 PM, Rich Shepard wrote:
> Something must have changed in the subversion repository and I want to
> confirm that this is a deliberate change.
... nothing was changed. The server operates as before.
> At least once a week when I'm working with grass I
On Thu, 21 Jun 2018, Markus Metz wrote:
No, they should not. They cover a part of that rectangle. You need to
patch coverages from different years together in order to get a more
complete coverage.
Markus,
Ah, I didn't realize this. That explains the why there are three files
with
Hello Veronica,
Thanks a lot it worked!!
following the line you wrote:
i.nightlights.intercalibration image=img1,img2,img3 suffix=c elvidge2014
and got the error:
(Thu Jun 21 17:36:56
2018)
i.nightlights.intercalibration
* Gabriel Cotlier [2018-06-21 18:24:38 -0300]:
Hello Veronica,
Thanks a lot it worked!!
Dear Gabriel,
Thanks for posting details and great it works. Don't worry about the
last image, there are no coefficients for F18 and 2013. We are forced
to skip this image in any analysis.
Details
26 matches
Mail list logo
