RE: Geo information

RE: Null error

2012-07-04T12:23:03Z

Evgenia, I need some more information about what's going on. Could you please provide the complete command-line output text. If you use 'gpt', please use also the -e switch (= print exception stack trace). For all other BEAM command-line tools use the -d (debug output) switch. In the $BEAM_HOME/config/beam.config file please make sure that

beam.consoleLog = true
beam.logLevel = ALL
beam.debug = true

Thanks!

RE: Null error

2012-06-29T14:59:06Z

Dear Evgenia,

This is probably a known issue. We provide an update soon.

In the meantime, try this: point your file exporer into the $BEAM_HOME/config directory.
Open "beam.config" in a text editor
Locate the line "# beam.pixelGeoCoding.useTiling = false" and change it to

beam.pixelGeoCoding.useTiling = false

by removing the leading hash.

If you are on Windows 7, you will need to copy the file to your desktop first, change it, then copy back.
Hopefully this helps.

Cheers
Norman

RE: VEGETATION-2 geolocation

2012-06-28T16:14:21Z

Hi Chris,

the VGT-2 P1 product reader has been developed quite while ago, but this geo-coding issue has never been reported. Possibly there where format changes meanwhile. I will need to hava a look at your specific file. Could you please provide it?

Regards
Norman

RE: Ingestion and processing of SPOT 5 data

2012-06-21T12:28:57Z

Dear Will, regarding your firest issue: The BEAM-DIMAP is a derived DIMAP profile, we currently can't read the SPOT DIMAP. However, you should be able to open the GeoTIFF raster data files within a SPOT5 dataset.

Regarding your second issue: you are right, the NASA SeaDAS group exchanges their (IDL-based) user interface by a one that is based on BEAM VISAT. It should be released in early summer as part of SeaDAS 7. All the processing code will remain in C, the GUI code will be Java, but you will be able to call all SeaDAS processors from within the GUI. Secondly, with SeaDAS 7 you will be able to read ALL the data products offered by the NASA OceanColour site.

Furthermore we extended VISAT in BEAM 4.10 (in collaboration with NASA) in order to read in-situ data (CSV files) and to use it in various plots and analyses, e.g. scatter plot and profile plots. This will also be possible in the new SeaDAS 7.

Hope this helps!

Norman

RE: Some question about SMOS BOX usage under Beam’s circumstance

2012-06-14T16:14:49Z

Dear Yuli Chen,

Quick answer for your point 2: Just add a pin, the open the pin manager (the icon with the pin plus a manager-kind-of-guy), select your pin in the table. Double-clicking cells in the 'Lat' or 'Lon' columns let you edit the lat/lon coordinate of a pin. It will then ju7mp to that position in the image view.

In the pixel view, you can then select "snap to selected pin" in order to display all pixel values there. If you only see the value of the currently open view, then go into the VISAT preferences dialog, entry "UI Behaviour" and select "show pixels of all bands". Using the pin manager you can also export all data under selected pins to a text file.

Regarding yor point 1, we have to investigate a bit in order to reproduce what's going on.

Regards
Norman

RE: band math gives bad result

2012-05-16T10:05:11Z

Hi Evgenia,

Sorry for not catching up for so long. Do you still suffer from your problem? If so, please attach the XML file, there must be something wrong with the file format, since "CDOM_Kow" is not part of your expression.

Norman

RE: MERIS Ocean Color L2 Reprojection

2012-05-02T14:23:50Z

Dear Erika,

are you using the latest BEAM 4.9.0.1? I remember there was a fix regarding MERIS FRS a while ago. Also BEAM 4.10 is quite stable now so that you could consider giving the latest development snapshot a try.

Best regards
Norman

RE: band math gives bad result

2012-05-02T14:15:27Z

Dear Evgenia,

Evgenia Gurova:

How should I modify it for using in GPF xml-file.. I try to put it there, but it seems to be some syntactics problem which i can not recognize..editor also highlight it with red starting from "<= 1"...

You can't use "<" and ">" directly in an XML file. You have to write "<" instead of "<" and ">" instead of ">". Sorry for this inconvenience (I hate it as well). Alternatively, you can encode the entire expression as CDATA. For example:

1<maskExpr><![CDATA[
2reflec_6 >= 0.0 && reflec_6 <= 1.0
3]]></maskExpr>

See http://www.w3schools.com/xml/xml_cdata.asp

Best regards
Norman

RE: Writer interface

2012-03-27T11:10:04Z

Luis, sounds good. Please request the pull!

Regards
Norman

RE: pconvert changed from 4.6.1 to 4.9.0.1?

2012-02-27T15:50:03Z

Pauline Cocevar:

Hello Beam Team,
Debug output:

reading file 20120204-ATS_NR_2P-UPA-L2P-51941.nc
creating histogram for band 'lat'...

Dear Pauline, the debug output is from BEAM 4.9, right?
-- Norman

RE: Reprojection to sphere, Mercator

2012-01-31T11:01:21Z

Hi Andrey,

the WKT used in BEAM is compliant to the following specification:
http://www.geoapi.org/2.0/javadoc/org/opengis/referencing/doc-files/WKT.html

You don't need to know the EPSG code.

Best regards
Norman

RE: Help system: javax.help.BadIDException

2011-11-09T13:54:10Z

Hi Sean,

I fixed it by adding a (missing) dependency to beam-help module to your seadas-app/pom.xml:

1
2       <dependency>
3          <groupId>org.esa.beam</groupId>
4          <artifactId>beam-help</artifactId>
5          <version>4.10-SNAPSHOT</version>
6       </dependency>

If you want a branded or otherwise customised SeaDAS help (I guess so), you should create your owen seadas-help module (copy beam-help module and rename stuff).

More customisation could be done in your seadas-app/src/main/resources/module.xml. For example, you could remove the default actions from the VISAT help menu:

1
2 <extension point="beam-ui:applicationDescriptors">
3       <applicationDescriptor>
4          <applicationId>SeaDAS</applicationId>
5          <displayName>SeaDAS</displayName>
6          <version>7.0-SNAPSHOT</version>
7          <buildId>${beam.build.id}</buildId>
8          <buildDate>${beam.build.date}</buildDate>
9          <excludedActions>
10             
11             
12             <id>helpTopics</id>
13             <id>showHomePage</id>
14             <id>showDataSources</id>
15             <id>about</id>
16          </excludedActions>
17          <excludedToolViews>
18             
19             
20          </excludedToolViews>
21       </applicationDescriptor>
22 </extension>

If you want to add your own help menu actions, you need to also define them in seadas-app/src/main/resources/module.xml. For example:

1
2 <extension point="beam-ui:actions">
3
4       <action>
5          <id>showObpgHomePage</id>
6          <parent>help</parent>
7          <class>gov.nasa.obpg.seadas.actions.ShowObpgHomePageAction</class>
8          <text>SeaDAS Home Page</text>
9          <description>Opens the SeaDAS home page.</description>
10          <placeAfter>helpTopics</placeAfter>
11       </action>
12
13 </extension>

RE: Graticule layer problem

2011-11-04T08:50:43Z

Great! I can still program BEAM

RE: Graticule layer problem

2011-11-03T13:03:16Z

Hi Sean,

Sean Bailey:

Any thoughts? Is there a way to prevent NaNs from getting through?

Yes, probably. I've just pushed a possible fix, see http://www.brockmann-consult.de/beam-jira/browse/BEAM-1354

Norman

RE: bug in epr_api_c

2011-03-14T08:08:18Z

Thanks François, we'll apply the patch asap. Alternatively, we could add you to the list of epr_c_api code contributors on github. After a brief discussion with the BEAM developers, you could then patch it yourself. What do you think?
Best regards
Norman

RE: [ANN] python bindings for EPR-API

2011-03-14T08:01:59Z

Dear Antonio,

that's great news! If you like, we can add a link to your site on our download page.

Best regards
Norman

RE: gpt Subset

2010-08-20T10:05:49Z

Hola Luis,

There is a tiny but important bug in your "launch_Subset.xml" file. Please remove the double quotes from the values of the <tiePointGridNames> and <bandNames> tags. Then it should work.

We are currently investigating the strange and confusing "SLF4J" output. Actually you should get a correct error message telling you what's wrong with the "launch_Subset.xml".

Saludos
Norman & Marco (Z.)

RE: epr-api - problem reading tie-point related information (coords, angles

2010-07-16T14:51:36Z

Thanks François, we will have a look into this problem and provide a fix for that asap.
Regards
Norman

RE: epr-api - problem reading tie-point related information (coords, angles

2010-07-16T10:09:32Z

Hi Simon,

Thanks for your C-API report! Your code really looks brilliant, I've just compiled it on Windows and tested it with your AATSR data. It seems to work just as expected, see attached "latitude_dump.txt". We will try 64bit Linux later this day. Maybe there is a 64bit problem in the epr_api, which has been developed on a 32bit computers at that time (which is a while ago).

Best regards
Norman

Re: P.P.S: Yes, I do. Mine is really boring compared to yours.
Re: P.P.P.S: There should be an attachment configuration setting somewhere, must find and ask our web admin...

RE: Geo information

2010-07-15T16:13:03Z

Hi zhongping, here is the data type translation table:

============================================
ENVI header entry <--> BEAM-DIMAP XML element
============================================
data type = 1 <--> <DATA_TYPE>int8</DATA_TYPE>
data type = 2 <--> <DATA_TYPE>int16</DATA_TYPE>
data type = 12 <--> <DATA_TYPE>uint16</DATA_TYPE>
data type = 3 <--> <DATA_TYPE>int32</DATA_TYPE>
data type = 4 <--> <DATA_TYPE>float32</DATA_TYPE>
data type = 5 <--> <DATA_TYPE>float64</DATA_TYPE>

Norman