Hi Ibon,
please try with contact at cyberlightning.com
Let me know
regards,
Pasquale
Il 13/07/2015 13:16, Ibon Salbidegoitia ha scritto:
> Hi Juha,
>
> I have seen from an automatic reply email that Sami is going to be on
> holidays till 31st of July. Is there any other technical support who
> can give me feedback about the Fiware Enabler developed by Cyberlightning?
> Best regards,
>
> Ibon
>
>
> 2015-07-13 11:10 GMT+00:00 Ibon Salbidegoitia <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>:
>
> Hi Sami,
>
> I haven't received reply for the issue I told you in my previous
> email.
> Can you please confirm me that you received? If so, can you tell
> me the situation?
> Should I put Juha in Cc for all this process?
> Thank you in advance. Best regards,
>
> Ibon
>
>
> 2015-07-01 17:20 GMT+00:00 Ibon Salbidegoitia
> <ibon.salbi at gmail.com <mailto:ibon.salbi at gmail.com>>:
>
> Hi Sami,
>
> First of all, as I mentioned in a previous email, I have put
> in Cc our Fiware Accelerator (Finodex) coaches as they
> requested in a meeting with them to follow the situation of
> each project that they are supporting.
>
> About your previous email, the last release is working! I have
> test it in our test server (http://151.80.143.120/GIS_4.3.3/)
> and the DEM works with the data provided as test.
> I have checked that the test requires the textures to have
> "texture" on their names and "DEM" for terrain DEM. I have
> upload my data to test it but I have the following problems:
>
> 1. When I preview your DEM (DEM_geotiff_terrain_EPSG3067) I
> can see on geoserver a grayscale image on openlayers
> (openlayers example
> <http://151.80.143.120:8080/geoserver/fiware/wms?service=WMS&version=1.1.0&request=GetMap&layers=fiware:DEM_geotiff_terrain_EPSG3067&styles=&bbox=374010.0,7547990.0,380020.0,7554000.0&width=512&height=512&srs=EPSG:3067&format=application/openlayers>).
>
> I have seen that the tiff is a float32 image in grayscale
> with a 281.604 minimum value and 792.834 maximum value .
>
> I have upload a similar DEM called "DEM_ODE_terrain" that
> it can be selected from the DEM GIS Client example (on
> previous link). This image is also float32 tiff with a
> minimum value of -3.40282e+38 and maximum of 1545.84,
> where minimum value is a NoData value as it is shown with
> gdalinfo command: NoData Value=-3.4028234663852886e+38
> The TIF image I use it can be found here:
> ftp://ftp.geo.euskadi.net/lidar/MDE_LIDAR_2013_ETRS89/MDT_LIDAR_2013_25m_ETRS89.zip
> The geodesic system of this TIF is ETRS89 that correponds
> to SRS EPSG:25830. However the preview seems to be a 0-1
> grayscale image as you can see here
> <http://151.80.143.120:8080/geoserver/fiware/wms?service=WMS&version=1.1.0&request=GetMap&layers=fiware:DEM_ODE_terrain&styles=&bbox=461050.0,4700750.0,606500.0,4811750.0&width=512&height=390&srs=EPSG:25830&format=application/openlayers> (takes
> some seconds as it is big). This could be due to the
> NoData values that make range so big not taking into
> account that the data does not exist. This is correct?
>
> 2. The Terrain texture also has been uploaded to Geoserver as
> can be seen here
> <http://151.80.143.120:8080/geoserver/fiware/wms?service=WMS&version=1.1.0&request=GetMap&layers=fiware:ODE_terrain_texture_orto&styles=&bbox=-3.480675981601883,42.457568610196404,-1.6858572736097794,43.45901565397562&width=591&height=330&srs=EPSG:4326&format=application/openlayers>.
> The DEM testing client gives the oportunity to select both
> layers mentioned (for terrain DEM + terrain texture),
> however nothing appears, only one small gray square
> looking upwards (on zenith) with the camera on the client
> as the altitudes are higher than the ones from the examples.
>
> So everything from test seems to work correctly, but when I
> introduce my data, the DEM test client does not seem to work.
> Could it be due to NoData values? Anyway, why the ortophoto
> inserted is shown as gray layer?
>
> Best regards,
> Ibon
>
>
> 2015-06-30 11:33 GMT+00:00 Sami J
> <sami.jylkka at cyberlightning.com
> <mailto:sami.jylkka at cyberlightning.com>>:
>
> Hi Ibon,
> sorry about late response. We have now made new release
> from both server and example client, these can be found
> from the forge under *MIWI-GISDataProvider 4.3.3*-release:
> https://forge.fiware.org/frs/?group_id=7
> source code has been uploaded also to the github.
>
> Short documentation related using DEM images can be found
> from:
> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_User_and_Programmers_Guide#World_Wind_Format_Module
>
> Installation document covers how to upload DEM image to
> geoserver:
> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_Installation_and_Administration_Guide#GeoTIFF_based_.28DEM.29_data_sets_for_elevation
>
>
> Regarding using latitude/longitude coordinates, I don't
> know if you are using them or not. I just wanted to
> mention this if you haven't noticed this information from
> the GIS GE documentation :) To elaborate further, provided
> GIS GE example web client has been implemented so that it
> works correctly only with metric coordinate system. Using
> lat/long data source won't work with the provided client,
> and that's why lat/long coordinate handling needs to be
> implemented by yourself. But as said, I don't know if you
> are using data source based in latitude/longitudes or
> metric coordinates.
>
>
> Best regards,
> Sami
>
> On Thu, Jun 25, 2015 at 11:53 AM, Ibon Salbidegoitia
> <ibon.salbi at gmail.com <mailto:ibon.salbi at gmail.com>> wrote:
>
> Hi Sami,
>
> I have a couple of things to ask.
>
> 1. It is great that the grayscale images for
> elevation is pretty much ready. Can you tell me
> when do you expect to finish the test and when I
> can be able to test it?
> 2. About the last paragraph, I do not understand why
> you tell me that lat/long is not supported. Where
> I have used it? Do you refer to the bounding box
> of the layers I have upload? So do I have to
> change the SRS to EPSG:25830 for example instead
> of EPSG:4326?
>
> Best regards,
> Ibon
>
>
> 2015-06-24 14:22 GMT+00:00 Sami J
> <sami.jylkka at cyberlightning.com
> <mailto:sami.jylkka at cyberlightning.com>>:
>
> Hi Ibon,
> ok now it's clear; in a short problem is that
> elevation data in grayscale image is not yet
> supported by the GIS GE.
>
> The good thing is that implementation for it is
> pretty much ready, we are doing final testing for
> it and then documentation will be updated. So soon
> it is possible to use grayscale elevation images
> as for source to elevation data, GIS GE
> implementation supports same data format as SRTM
> data uses. GIS GE will send response data in
> octet-stream format, client itself needs to create
> 3D objects based on the octet-stream data.
>
> please note that current version of the GIS GE
> reference web client only supports metric
> coordinates, Lat/log is not working. I mention
> this because if you'd like to use GIS data in
> Lat/Log format, the client scenemanager logic
> needs to be re-implemented.
>
> Best regards,
> Sami
>
>
> On Wed, Jun 24, 2015 at 10:10 AM, Ibon
> Salbidegoitia <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>> wrote:
>
> Hi Sami,
>
> I have upload the ortophoto on "fiware"
> workspace and also texture with appropriate
> names to be able to see them in my Client
> examples:
> +
> http://151.80.143.120/GIS_4.3.2/GIS_Client_octet-stream/index.xhtml
> +
> http://151.80.143.120/GIS_4.3.2/GIS_Client_xml3d/index.xhtml
>
> As you will see, selecting the terrain
> texture, the new layer appears (surprisingly,
> the one of other workspace also). But if I try
> to select the terrain layer (first box of GIS
> client), you will see that the one uploaded
> with the name "ODE_test_terrain" does not
> appear. Maybe I didn't explain correctly in my
> previous email, but this layer is the altitude
> layer, the shape. So I suppose that the W3DS
> options have to be defined, but if you access
> to that layer on our testing server
> (http://151.80.143.120:8080/geoserver . User:
> admin Pass: geoserver) you will see that I
> cannot access to the W3DS tab of
> "ODE_test_terrain" layer to make it "Active"
> and "Queryable" and maybe other options
> required on the GIS client to be able to
> require it as the shape of the terrain.
>
> Which could be the problem?
>
> Just one more thing. I am selected on one of
> the FIWARE accelerators (Finodex) to develop
> services with Fiware tools. As you imagine,
> this enabler is one that I am using. They
> required me to put them (fiware coaches of
> Finodex accelerator) in CC on this discussion
> emails to follow the evolution of our project.
> So I will put them in CC on the next email. I
> suppose there is no problem on this, is it?
>
> Best regards,
> Ibon
>
>
> 2015-06-23 8:38 GMT+02:00 Sami J
> <sami.jylkka at cyberlightning.com
> <mailto:sami.jylkka at cyberlightning.com>>:
>
> Hi Ibon,
> thank you for the feedback, I need to
> update user guide about this issue.
> Textures are queried via geoserver's
> WMS-interface. This interface isn't
> related to W3DS-module and therefore
> there's no need to declare W3DS related
> options for the texture layer. So when you
> define texture layer which you want to use
> as a texture for 3D terrain, it is enough
> to define options under "Data"-tab.
>
> Best regards,
> Sami
>
> On Mon, Jun 22, 2015 at 6:21 PM, Ibon
> Salbidegoitia <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>> wrote:
>
> Hi Sami,
>
> Thank you. Yes I knew that because I
> saw it in the JS code you mention.
> I was going to change the ortophoto
> and texture to workspace to "fiware"
> for that reason, but being honest I
> didn't test it because I found the
> error I described in my previous
> email. I mean, I was trying to access
> the texture layer W3DS tab to make it
> "Active" and "Queryable" as required
> on the wiki, so that's the reason I
> sent you the error, because I though
> that it wouldn't be possible to go
> ahead without changing the texture the
> configuration.
>
> So, if I am wrong and it is not
> necessary to configure the W3DS tab, I
> will try it. I don't need from you to
> change the JS code to find texture and
> photos of all the workspace. I will
> change the data to "fiware" workspae.
>
> I will tell you if everything goes well.
> Best regards,
>
> Ibon
>
>
> 2015-06-22 9:05 GMT+02:00 Sami J
> <sami.jylkka at cyberlightning.com
> <mailto:sami.jylkka at cyberlightning.com>>:
>
> Hi Ibon,
> nice to hear you have been able to
> progress in your work!
>
> Let me answer behalf Juha: Your
> texture data seems to be ok. In
> case you are using GIS GE
> reference client problem with the
> texture loading might be with the
> used workspace. GIS GE reference
> client assumes that all data is in
> "fiware"-workspace. This applies
> also for the textures. So changing
> texture workspace to "fiware"
> might solve loading problem.
>
> If you'd like to modify reference
> client to support also other
> workspaces, URI for texture
> loading is defined in the
> scenemngr.js getElements-function.
> You can modify URL created in there.
>
> Best regards,
> Sami
>
>
> On Mon, Jun 22, 2015 at 9:05 AM,
> Juha Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>
> wrote:
>
>
> ---------- Forwarded message
> ----------
> From: *Ibon Salbidegoitia*
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> Date: Thu, Jun 18, 2015 at
> 11:05 AM
> Subject: Re: W3DS - FIWARE
> To: Juha Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>
>
>
> Hi Juha,
>
> I checked that many changes
> where done on the data and
> wiki. Congratulations! Now
> everything is very clear!
>
> I write you because I have
> some doubts about the texture
> data. On the wiki "User and
> Programmers Guide" section
> "3.3.3 Adding texture" the
> last sentence says that one
> option is to store texture on
> a GeoTIFF.
> I used the following GeoTIFF
> texture (MDT) data on float32
> format to try it. You can
> download it here:
> ftp://ftp.geo.euskadi.net/lidar/MDE_LIDAR_2013_ETRS89/MDT_LIDAR_2013_25m_ETRS89.zip
>
> The file has been uploaded to
> Geoserver. As it does not
> recognize the SRS, I defined
> whichis the EPSG:25830.
> As it says in the Unit Testing
> Plan, I have to go to W3DS tab
> to activate and make it queryable.
> However, it returns an error
> on JIRA.
>
> You can check it in our geoserver:
> http://151.80.143.120:8080/geoserver/
> + User: admin
> + Pass: geoserver
>
> The GeoTIFF texture is defined
> on the layer "terrain" , on
> workspace "ODE"
> Please let me know why this
> option is not available.
> Best regards,
>
> Ibon
>
>
> 2015-06-02 18:20 GMT+02:00
> Ibon Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>:
>
> Hi Juha,
>
> I have been able to run
> GIS Client examples:
> +
> http://151.80.143.120/GIS_4.3.2/GIS_Client_octet-stream/index.xhtml
> +
> http://151.80.143.120/GIS_4.3.2/GIS_Client_xml3d/index.xhtml
>
> As you can see in the
> attached pictures, there
> seems to be some problems
> with space between layers
> and I cannot see the xml3d
> buildings on the examples.
> Do you know where the
> buildings should appear?
>
>
> Just as comment, I have
> found more bugs that may
> improve the Unit Testing
> Plan. I list all of them
> below if you are
> interested on changing them
>
> *On wiki*:
> 1.2.2.4 PostGIS connection
> to GeoServer
> + When Publish
> fiware_test_terrain PostGIS -
> PostGIS Database
> In "Objects
> Attributes" section select
> "name" for the "Object ID"
> it is not possible because
> only options are
> [elevation / geom / lod].
> The documentation seems to
> need to select "name" when
> it does not exist.
>
> 1.2.3.2
> terrain_texture_orto.tif
> and terrain_texture_raster.tif
> + Raster_map_image_for_terrain_texture/terrain_texture_raster.tif
> SRS is automatically set
> toEPSG:404000. Not
> EPSG:3067 as it is said on
> the wiki
> + Aero_photo_for_terrain_texture/terrain_texture_orto.tif
> SRS is automatically set
> toEPSG:3067. Not
> EPSG:404000 as it is said
> on the wiki
>
> *On GIS Client*:
> Version 4.3.2
> + The both examples ()
> have changed the script
> "map.js" and now it is not
> automatically defined
> "baseUrl" variable as
> previous version 4.2.2. It
> will be recommended to use
> the code lines:
> var ip = location.host;
> var baseUrl =
> "http://"+ip+"/geoserver/";
>
> *On MIWI-GISDataProvider
> download section*:
> + Version 4.3.2
> - Test assest 4.3.2 ZIP
> file has a space between
> text and version numbers
> ->
> https://forge.fiware.org/frs/download.php/1645/Test_asset_%204.3.2.zip
> - ZIP file when
> decompressed has a folder
> with a space between text
> ("rel") and numbers
> ("4.3.2") -> rel\ 4.3.2
> - Subfolders of
> Test_assest
> "Building_coordinates /"
> and
> "PostGIS_database_backup
> /" have a space at the end
> of the name.
> + Version 4.2.2
> - Subfolders of
> Test_assest
> "Building_coordinates /"
> and
> "PostGIS_database_backup
> /" have a space at the end
> of the name.
>
> Best regards,
>
> Ibon
>
>
> 2015-06-02 11:59 GMT+00:00
> Juha Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi Ibon,
>
> Thank you for feedback
> about test asset
> naming problems, I
> wasn't aware of those
> and I have informed my
> colleague who have
> made those packages.
> He will fix those
> tomorrow.
>
> Building coordinates
> are needed if you want
> to use external 3D
> models in your
> application with real
> spatial information.
> For example hand made
> building models placed
> in correct position
> etc. If you don't need
> those then that step
> is optional.
>
> We also updated guide
> for database restoring
> and it can be found
> from here:
> https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_Unit_Testing_Plan#Import_PostGIS_database_backup_with_terrain_data
>
> Your problem was that
> username in the
> database backup was
> defined to be 'sami'
> and it does not exist
> in your system. It is
> fixed by ignoring
> username from the
> database backup.
>
> Before restoring that
> database backup you
> should drop
> fiware_test_terrain table.
>
> Let me know if this
> was helpful.
>
> - Juha
>
> On Tue, Jun 2, 2015 at
> 11:41 AM, Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Sorry I send
> previous email
> without finishing
> the email as
> error. You have
> below all the email.
>
> Hi Juha,
>
> Sorry for the
> delay, I was busy
> and these last 3
> days I had some
> problems with
> tomcat so I
> decided to format
> everything and
> start from the
> beginning to know
> what errors are
> happening.
> I will try to
> explain
> cronologically all
> the steps and
> error/bugs found.
>
> First of all I
> update git
> repository and
> change to the
> "fiware_rel_4.x"
> branch to create
> the WAR file with
> the maven
> command: mvn
> install
> -DdownloadSources=true
> -DskipTests=true
> -Pw3ds
> After restarting
> tomcat, the
> geoserver seems to
> work ->
> http://151.80.143.120:8080/geoserver
> (User: admin /
> Pass: geoserver)
> I did not use the
> WAR published, I
> created my own
> from the new
> github branch as
> you see.
>
> So then I decided
> to update the test
> unit plan. Here I
> have one comment
> just to improve in
> case you want. I
> have checked that
> you usually use
> "space" on folders
> and files which
> usually is no
> suitable. I refer
> specificly to the
> 4.3.2 version.
> + The ZIP file
> has a "space" on
> the name what
> requires to use
> ASCI character to
> download: wget
> --no-check-certificate
> https://forge.fiware.org/frs/download.php/1645/Test_asset_%204.3.2.zip
> + When ZIP is
> decompressed, the
> name of the folder
> has also a
> "space": /home/UnitTestPlan/rel\
> 4.3.2
> + PostGIS
> database backup
> has also a "space"
> at the
> end: /home/UnitTestPlan/rel\
> 4.3.2/PostGIS_database_backup\
> /
>
> Any way, I
> continue with the
> database restore.
> On the PostGIS
> database backup, I
> checked on the
> 4.3.2 version that
> there are 2
> files: building_coordinates
> and test_asset-terrain.
> The
> "building_coordinates" file
> appears to be a
> text format dump.
> So is this file
> necessary to
> upload to database?
> The
> "test_asset-terrain"
> could be uploaded
> to postgres with
> the following
> command: pg_restore -d
> fiware_test
> /home/UnitTestPlan/rel\
> 4.3.2/PostGIS_database_backup\
> /FIWARE-postgis-test_asset-terrain
> However, I receive
> the following errors:
> =================================================
> pg_restore:
> [archiver (db)]
> Error while
> PROCESSING TOC:
> pg_restore:
> [archiver (db)]
> Error from TOC
> entry 184; 1259
> 65659 TABLE
> fiware_test_terrain sami
> pg_restore:
> [archiver (db)]
> could not execute
> query: ERROR:
> role "sami" does
> not exist
> Command was: ALTER
> TABLE
> public.fiware_test_terrain
> OWNER TO sami;
>
> pg_restore:
> [archiver (db)]
> Error from TOC
> entry 183; 1259
> 65657 SEQUENCE
> fiware_test_terrain_id_seq
> sami
> pg_restore:
> [archiver (db)]
> could not execute
> query: ERROR:
> role "sami" does
> not exist
> Command was: ALTER
> TABLE
> public.fiware_test_terrain_id_seq
> OWNER TO sami;
>
> WARNING: errors
> ignored on restore: 2
> =================================================
>
> I checked the
> information stored
> from backup on the
> database and found
> the following
> tables, which I am
> not sure if they
> are all or there
> are some missing.
> =================================================
>
> List of relations
> Schema | Name
> | Type | Owner
> --------+----------------------------+----------+----------
> public |
> fiware_test_terrain
> | table |
> postgres
> public |
> fiware_test_terrain_id_seq
> | sequence | postgres
> public |
> geography_columns
> | view
> | postgres
> public |
> geometry_columns
> | view
> | postgres
> public |
> raster_columns
> | view
> | postgres
> public |
> raster_overviews
> | view
> | postgres
> public |
> spatial_ref_sys
> | table
> | postgres
> =================================================
>
> I did not continue
> because it seems
> that there are
> some errors that I
> should first
> understand and fix
> before continuing.
> If you need
> something else
> from my side,
> please let me
> know. And please,
> let me know if I
> have done
> something wrong.
> Thank you. Best
> regards,
>
> Ibon
>
>
> 2015-06-02 8:33
> GMT+00:00 Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>:
>
> Hi Juha,
>
> Sorry for the
> delay, I was
> busy and these
> last 3 days I
> had some
> problems with
> tomcat so I
> decided to
> format
> everything and
> start from the
> beginning to
> know what
> errors are
> happening.
> I will try to
> explain
> cronologically
> all the steps
> and error/bugs
> found.
>
> First of all I
> update git
> repository and
> change to the
> "fiware_rel_4.x"
> branch to
> create the WAR
> file with the
> maven
> command: mvn
> install
> -DdownloadSources=true
> -DskipTests=true
> -Pw3ds
> After
> restarting
> tomcat, the
> geoserver
> seems to work
> ->
> http://151.80.143.120:8080/geoserver
> (User:
> admin /
> Pass: geoserver)
> I did not use
> the WAR
> published, I
> created my own
> from the new
> github branch
> as you see.
>
> So then I
> decided to
> update the
> test unit
> plan. Here I
> have one
> comment just
> to improve in
> case you want.
> I have checked
> that you
> usually use
> "space" on
> folders and
> files which
> usually is no
> suitable. I
> refer
> specificly to
> the 4.3.2 version.
> + The ZIP
> file has a
> "space" on the
> name what
> requires to
> use ASCI
> character to
> download: wget
> --no-check-certificate
> https://forge.fiware.org/frs/download.php/1645/Test_asset_%204.3.2.zip
> + When ZIP
> is
> decompressed,
> the name of
> the folder has
> also a
> "space": /home/UnitTestPlan/rel\
> 4.3.2
>
>
>
>
> 2015-05-26
> 12:49
> GMT+00:00 Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi Ibon,
>
> That
> problem
> should now
> be fixed,
> code is in
> the github
> (https://github.com/Cyberlightning/geoserver/tree/fiware_rel_4.x)
> and we
> have also
> published
> new war
> file in
> Fiware
> FusionForge (https://forge.fiware.org/frs/download.php/1643/geoserver.war).
>
> We also
> updated
> test
> assets and
> reference
> client.
> Updated
> reference
> client is
> already
> available
> from the
> Github and
> test
> assets
> will be
> published
> later
> today or
> tomorrow
> morning to
> FusionForge under
> release
> 4.3.2
> (https://forge.fiware.org/frs/?group_id=7).
>
> I hope
> that this
> release
> will fix
> problems
> you
> encountered earlier.
> Please
> report
> back did
> this solve
> those
> problems.
> Thank you
> for
> submitting
> these bug
> reports.
>
> - Juha
>
> On Tue,
> May 26,
> 2015 at
> 9:33 AM,
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>
> wrote:
>
> Hi Ibon,
>
> We
> have
> looked
> into
> that
> problem now
> for
> couple
> of
> days
> and it
> seems
> to be
> somehow related
> to
> Tomcat
> and
> system
> locale
> settings.
> We can
> reproduce
> same
> problem when
> we
> deploy
> to a
> Tomcat
> instance
> while
> with
> Jetty
> everything
> works
> just fine.
>
> I'm
> working with
> the
> fix
> now,
> but
> there
> is
> also a
> workaround:
> deploy
> war
> package to
> a
> Jetty
> instance.
>
> I will
> notify
> you
> once I
> have
> pushed
> code
> changes to
> git.
>
> - Juha
>
> On
> Fri,
> May
> 22,
> 2015
> at
> 1:08
> PM,
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>
> wrote:
>
> I
> also
> forgot
> to
> mention
> that
> you should
> move
> to
> newer
> test
> client
> which
> we
> will
> release
> officially
> during
> summer,
> but code
> is
> already
> available
> from
> the Github:
> https://github.com/Cyberlightning/Cyber-WeX
>
>
> Client
> code
> can be
> found
> from
> here:
> https://github.com/Cyberlightning/Cyber-WeX/tree/master/GIS/GIS_Client_xml3d
>
> - Juha
>
> On
> Fri,
> May 22,
> 2015
> at
> 12:30
> PM, Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>
> wrote:
>
> Hi
> Ibon,
>
>
> I have
> to
> admit
> that
> I'm
> clueless
> with
> that
> terrain
> problem,
> since
> I couldn't
> replicate
> it.
> Everything
> seems
> to
> be
> right
> at
> the
> server
> side
> but
> still
> data
> is
> somehow
> corrupted
> when
> it
> arrives
> to
> the
> client.
> We
> have
> deployed
> that
> same
> data
> set
> without
> any
> problems
> to
> more
> than
> 20
> different
> systems
> by
> many
> different
> users
> during
> our
> internal
> development
> and
> testing.
>
> There
> are
> still
> few
> points
> which
> you
> could
> try.
> 1.
> Install
> newer
> PostGIS
> version
> for
> example
> from
> Ubuntu
> repositories
> instead
> of
> manually
> build
> one.
>
> 2.
> Try
> our
> upcoming
> release
> of
> Geoserver
> from
> Github.
> This
> shouldn't
> be
> difficult,
> since
> you
> already
> build
> your
> own
> version.
>
> If
> you
> used
> git
> to
> clone
> code
> earlier,
> you
> only
> need
> to
> pull
> new
> changes
> from
> the
> repository
> and
> change
> code
> branch
> from
> fiware
> to
> fiware_rel_4.x
> (git
> pull
> &&
> git
> checkout
> fiware_rel_4.x)
> and
> rebuild
> project.
>
>
> Also
> I created
> database
> dump
> from
> building
> coordinates
> table
> and
> it's
> as
> an
> attachment.
> We
> will
> add
> it
> also
> to
> the
> assets
> and
> update
> documentation
> once
> we
> have
> little
> spare
> time
> to
> do
> it.
> Table
> can
> be
> restored
> with
> command: sudo
> -u
> postgres
> psql
> databasename
> < path/to/the/file.sql
>
> Before
> restoring
> that
> dumb,
> change
> URLs
> in
> it
> to
> point
> a place
> where
> you
> actually
> have
> that
> xml
> file.
> At
> the
> moment
> URL
> is
> http://localhost/Test_asset/Building_model/building.xml
>
> - Juha
>
> On
> Thu,
> May
> 21,
> 2015
> at
> 1:09
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> You
> are
> right,
> I forgot
> to
> edit
> the
> tomcat7
> default
> start-up
> configuration
> file.
> Now
> is
> using
> openJDK.
>
>
> 2015-05-21
> 9:36
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> Could
> you
> restart
> tomcat
> again
> since
> it
> still
> uses
> Oracle
> java
> 1.8.
>
> - Juha
>
> On
> Thu,
> May
> 21,
> 2015
> at
> 10:57
> AM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> I checked
> that
> tomcat
> was
> down
> due
> to
> low
> xmx
> size.
> I restarted
> and
> modify
> xmx
> to
> avoid
> errors.
> Asnwering
> to
> your
> comments:
> +
> Please
> let
> me
> know
> when
> you
> update
> the
> documentation
> to
> check
> importin
> building
> coordinates
> +
> I imported
> with
> following
> command
> of
> postgres:
> $ su
> - postgres
> $ createdb
> fiware_test
> $ pg_restore
> -d
> fiware_test
> ./Test_asset_3.3/PostGIS_database_backup\
> /FIWARE-postgis-test_asset
>
> Because
> I am
> using
> remote
> server
> I cannot
> use
> pgadmin,
> but
> the
> import
> was
> correct
> without
> errors
> and
> I checked
> that
> the
> data
> was
> correct.
> +
> I am
> using
> Oracle
> java
> (1.8.0_31),
> so
> I will
> change
> it
> to openJDK7
> as
> you
> recommend.
> Now
> is
> changed
> to
> openJDK7
> to
> version
> 1.7.0_79
>
>
> As
> I said,
> the
> Geoserver
> is
> active,
> so
> you
> can
> check
> on
> it
> whatever
> you
> want.
> Kind
> regards,
>
> Ibon
>
>
>
> 2015-05-21
> 6:56
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> I was
> looking
> into
> those
> errors
> you
> reported
> but
> your
> server
> went
> down
> before
> I could
> figure
> out
> any
> final
> solution.
> Here
> are
> my
> thoughts
> so
> far.
>
> I noticed
> that
> something
> have
> went
> wrong
> at
> least
> with
> building
> coordinate
> importing
> and
> we
> will
> update
> documentation
> how
> to
> import
> those
> properly.
> I can
> notice
> you
> once
> that
> is
> done.
>
> I also
> would
> like
> to
> make
> sure
> that
> fiware:fiware_test_terrain
> is
> data
> set
> provided
> by
> us
> and
> you
> imported
> it
> to
> the
> database
> as
> instructed
> with
> pgAdmin?
>
> Third
> point:
> in
> the
> past
> I had
> some
> problems
> with
> Geoserver
> when
> we
> used
> Oracle
> java,
> so
> please
> make
> sure
> that
> you
> use
> openJDK7.
> You
> can
> check
> used
> Java
> version
> with
> commad:
>
> java
> -version
>
> result
> should
> be
> something
> similar:
> -----------------
> :~$
> java
> -version
> java
> version
> "1.7.0_79"
> OpenJDK
> Runtime
> Environment
> (IcedTea
> 2.5.5)
> (7u79-2.5.5-0ubuntu0.14.04.2)
> OpenJDK
> 64-Bit
> Server
> VM
> (build
> 24.79-b02,
> mixed
> mode)
>
> If
> not,
> change
> default
> java
> version
> with
> command:
> sudo
> update-alternatives
> --config
> java
>
> - Juha
>
> On
> Mon,
> May
> 18,
> 2015
> at
> 10:34
> AM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> The
> last
> couple
> of
> months
> I have
> been
> learning
> and
> understanding
> all
> the
> things
> that
> we
> discussed
> 2 months
> ago.
> Once
> I knew
> how
> to
> do
> most
> of
> the
> things,
> I tried
> to
> do
> the
> "Unit
> Testing
> Plan"
> from
> the
> Wiki
> (https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_Unit_Testing_Plan)
> I have
> found
> some
> bugs/errors
> that
> I think
> they
> should
> be
> corrected
> if
> possible:
> + Section:
> 1.2.2.3
> PostGIS
> connection
> to
> GeoServer
> + terrain_texture_raste
> has
> a EPSG:404000
> SRS
> (set
> by
> default)
> + terrain_texture_orto
> has
> a EPSG:3067
> SRS
> (set
> by
> default)
> + Section:
> 1.2.3.2
> terrain_texture_orto.tif
> and
> terrain_texture_raster.tif
> + On
> building_coordinates
> SRS
> is
> not
> automatically
> assigned
> + On
> building_coordinates
> table,
> when
> SRS
> EPSG:3047
> value
> is
> introduced
> manually,
> the
> "Bounding
> Box"
> values
> seem
> to
> be
> wrong
> assigned
> + Select
> Activate
> and
> Queryable
> in
> the
> W3DS
> Settings,
> it
> is
> not
> clear
> if
> it
> is
> for
> both
> tables
> + In
> Objects
> Attributes
> select
> name
> for
> the
> Object
> ID.
> Only
> for
> building_coordinates
> table,
> because
> fiware_test_terrain
> table
> has
> not
> got
> this
> Object
> ID.
>
> I have
> follow
> everything
> sucessfully
> but
> at
> the
> end,
> it
> is
> not
> possible
> to
> see
> the
> correct
> result
> (http://151.80.143.120/GIS/).
> I am
> not
> sure
> if
> it
> is
> for
> the
> "building_coordinates"
> bounding
> box
> values
> or
> what.
> You
> can
> check
> on
> Geoserver
> that
> everything
> is
> correct
> (http://151.80.143.120/geoserver
> User:
> admin
> Pass:
> geoserver.
> The
> server
> is
> a server
> to
> test
> this
> W3DS
> service
> only,
> so
> you
> can
> use
> it
> without
> any
> problems)
> So
> something
> seems
> that
> it
> is
> not
> correctly
> working.
> What
> can
> it
> be?
> (All
> the
> data
> was
> correctly
> imported
> to
> PostGIS
> without
> errors)
> Thank
> you
> in
> advance.
> Best
> regards,
>
> Ibon
>
>
> 2015-03-26
> 7:42
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> I have
> been
> out
> of
> office
> and
> didn't
> have
> time
> to
> reply
> earlier.
>
> EPSG:900913
> is
> map
> projection
> defined
> by
> Google
> and
> it's
> using
> lat/lon
> coordinates.
> At
> the
> moment
> requesting
> data
> from
> non-metric
> coordinate
> systems
> will
> result
> erroneous
> output.
> Some
> projection
> tools
> may
> use
> that
> as
> a default
> projection
> if
> it's
> undefined.
> I suggest
> that
> you
> check
> your
> projection
> definitions
> from
> importing
> code
> and
> if
> you
> didn't
> set
> any
> coordinate
> system
> set
> one.
>
> I also
> quickly
> checked
> that
> one
> tile
> you
> provided
> and
> there
> was
> a lot
> no-data
> values.
> You
> could
> probably
> get
> better
> results
> if
> you
> select
> input
> data
> from
> area
> where
> there
> are
> actually
> data
> to
> show.
>
> Please
> note
> that
> only
> UTM
> coordinate
> systems
> (or
> similar)
> are
> supported
> by
> W3DS
> module.
>
> For
> visualization
> you
> can
> use
> sample
> client
> provided
> within
> FIWARE
> project.
> It
> is
> quite
> simple
> and
> you
> shouldn't
> have
> any
> problems
> to
> understand
> how
> it
> does
> requests
> to
> the
> server
> and
> visualize
> received
> 3D
> data.
>
> - Juha
>
> On
> Wed,
> Mar
> 18,
> 2015
> at
> 10:11
> AM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> I have
> been
> searching
> and
> found
> that
> my
> data
> is
> in EPSG:900913
> and
> now
> the
> layer
> is
> published
> and
> I can
> see
> it.
> Is
> this
> the
> correct
> way
> to
> publish
> it?
> So
> now,
> I am
> supposed
> to
> use
> the
> 3D
> capabilities
> to
> visualize
> in
> 3D.
> I have
> checked
> the
> XML3D
> link
> that
> you
> sent
> me
> but
> I don't
> understand
> how
> I have
> to
> apply
> to
> visualize
> the
> layer
> in
> 3D.
> Can
> you
> please
> be
> more
> specific
> or
> give
> me
> some
> help?
> Thank
> you
> in
> advance.
> Kind
> regards,
>
> Ibon
>
>
> 2015-03-18
> 7:13
> GMT+00:00
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>:
>
> Hi
> Juha,
>
>
> I have
> been
> able
> to
> introduce
> the
> XYZ
> files
> (*.asc
> in
> my
> case)
> to
> the
> Postgre
> database
> with
> the
> PostGIS
> extension.
> I am
> able
> to
> see
> the
> layer
> from
> the
> Geoserver
> but
> I have
> some
> doubts
> about
> the
> data
> to
> be
> introduced
> that
> I don't
> know
> how
> to
> fill
> when
> Geoserver
> asks
> for
> publishing
> the
> layer.
> I have
> followed
> the
> following
> command
> lines
> to
> introduce
> the
> data
> to
> database
> which
> I will
> appreciate
> if
> you
> can
> tell
> me
> if
> they
> are
> correct.
> And
> also,
> I would
> like
> to
> know
> how
> can
> I publish
> the
> layer
> because
> the
> link
> that
> you
> send
> me
> doesn't
> give
> me
> enough
> information
> to
> be
> able
> for
> that.
>
> ==============================================================================================================
> =====
> Download
> the
> XYZ
> data
> as
> *.asc
> file
> =====
> $ mkdir
> /root/data
> $ cd
> /root/data
> $ wget
> ftp://ftp.geo.euskadi.net/lidar/MDE_LIDAR_2013_ETRS89/MDT/H0037/mdt_037_1_8.zip
> $ unzip
> mdt_037_1_8.zip
> $ gdal_polygonize.py
> -f
> "ESRI
> Shapefile"
> mdt_037_1_8.asc
> mdt_037_1_8.shp
>
> =====
> Create
> database
> on
> Postgre
> as
> postgres
> user
> =====
> $ su
> - postgres
> $ psql
> -U
> postgres
> -d
> postgres
> $ create
> database
> [yourdatabase];
> ->
> CREATE
> DATABASE
> $ \list
> $ \q
> $ psql
> -d
> [yourdatabase]
> -c
> "CREATE
> EXTENSION
> postgis;"
> ->
> CREATE
> EXTENSION
> $ exit
>
> =====
> Define
> Postgre
> password
> =====
> $ psql
> -U
> postgres
> $ \password
> postgres
> $ \q
> $ exit
>
> =====
> Import
> data
> with
> "shp2pgsql"
> utility
> of
> postgis
> (http://www.bostongis.com/pgsql2shp_shp2pgsql_quickguide.bqg)
> =====
> $ /root/postgis-2.1.0/loader/shp2pgsql
> /root/data/mdt_037_1_8.shp
> >sql
> ->
> Shapefile
> type:
> Polygon
> ->
> Postgis
> type:
> MULTIPOLYGON[2]
>
> =====
> Import
> created
> sql
> to
> postgre
> =====
> $ mv
> sql
> /var/lib/postgresql/
> $ chmod
> 777
> /var/lib/postgresql/sql
> $ su
> - postgres
> $ psql
> -U
> postgres
> -d
> [yourdatabase]
> -f
> sql
> $ psql
> -U
> postgres
> -d
> [yourdatabase]
> -c
> "\d"
> ->
> List
> of
> relations
> ->
> Schema
> |
> Name
> |
> Type
> |
> Owner
>
> ->
> --------+---------------------+----------+----------
> ->
> public
> | geography_columns
> |
> view
>
> | postgres
> ->
> public
> | geometry_columns
> |
> view
> | postgres
> ->
> public
> | mdt_037_1_8
>
> |
> table
> |
> postgres
> ->
> public
> | mdt_037_1_8_gid_seq
> | sequence
> | postgres
> ->
> ...
>
> $ exit
>
> =====
> Add
> new
> workspace
> =====
> + Name:
> Fiware
> + URI
> of
> name
> space:
> com.fiware
>
> =====
> Add
> new
> "Data
> store"
> on
> Geoserver
> (http://151.80.143.120:8080/geoserver)
> =====
> + Select
> the
> "PostGIS
> - PostGIS
> Database"
> vectorial
> data
> + Add
> data
> required:
> + Workspace:
> Fiware
> + Name
> of
> origin
> data:
> Fiware_Test1
> + database:
> fiwaretest1
> + host:
> localhost
> + port:
> 5432
> + user:
> postgres
> + pass:
> postgres
>
> =====
> Add
> new
> layer
> and
> make
> public
> =====
> + Edit
> layer
> features?¿?
> + SRS?
> + ...
>
> ==============================================================================================================
>
> Thank
> you.
> Kind
> regards,
>
> Ibon
>
> 2015-03-03
> 13:42
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> Yes,
> write
> all
> polygons
> to
> a single
> shp
> file
> or
> to
> a single
> table
> inside
> a database
> and
> you
> are
> good
> to
> go.
>
>
> I would
> recommend
> that
> you
> also
> study
> some
> basics
> about
> rendering
> engines
> and
> search
> general
> knowledge
> what
> data
> 3D
> models
> really
> keeps
> inside
> them.
>
>
> In
> FIWARE
> we
> use
> XML3D
> as
> a rendering
> engine
> and
> all
> 3D
> models
> produced
> by
> GeoServer
> are
> in
> XML3D
> format.
> Here
> is
> one
> guide
> how
> to
> use
> XML3D
> rendering
> engine:
> https://github.com/xml3d/xml3d.js/wiki/The-Basics-of-XML3D
>
> On
> Tue,
> Mar
> 3,
> 2015
> at
> 2:53
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> Thank
> you
> for
> your
> clarifications.
> I have
> some
> doubts
> about
> your
> comments.
> I understand
> how
> do
> I have
> to
> create
> the
> polygons.
> I have
> done
> a python
> script
> with
> the
> for
> loops
> as
> you
> said
> (attached)
> which
> creates
> the
> POLIGONZs.
> I have
> done
> a SHP
> file
> for
> each
> polygon,
> but
> should
> I do
> a single
> SHP
> with
> all
> the
> polygons?
> I suppose
> that
> I should
> do
> a single
> SHP
> because
> I can
> have
> many
> polygons
> if
> the
> resolution
> is
> too
> high.
> Or
> this
> is
> not
> possible?
> The
> procedure
> of
> writting
> data
> to
> database
> with
> psycopg2
> is
> similar,
> so
> the
> same
> question,
> all
> polygons
> together
> is
> it
> possible?
> Kind
> regards,
>
> Ibon
>
>
> 2015-03-03
> 11:35
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> I have
> just
> updated
> User
> and
> Programmers
> guide.
> I hope
> that
> these
> tips
> helps
> you
> forward.
> Added
> content:
>
> Data
> generation
> from
> *.xyz
> file
> format
>
> Here
> is
> a small
> sample
> from
> source
> dataset:
>
> Easting
> Northing
> Elevation
> ---------------------------------
> 398000.000
> 7542000.000
> 279.950
> 398010.000
> 7542000.000
> 279.388
> 398020.000
> 7542000.000
> 278.818
> 398000.000
> 7541990.000
> 281.002
> 398010.000
> 7541990.000
> 280.436
> 398020.000
> 7541990.000
> 279.847
> 398000.000
> 7541980.000
> 282.096
> 398010.000
> 7541980.000
> 281.539
> 398020.000
> 7541980.000
> 280.944
>
>
> That
> data
> produces
> following
> 2D
> grid:
>
>
>
> 0
> 1
>
>
> 2
> |-------------------------------------------------|---------------------------------------------------|-------------------------------------------------|
> 0 |
> 398000.000
> 7542000.000
> 279.950
> |
> 398010.000
> 7542000.000
> 279.388
> |
> 398020.000
> 7542000.000
> 278.818
> |
> |-------------------------------------------------|---------------------------------------------------|-------------------------------------------------|
> 1 |
> 398000.000
> 7541990.000
> 281.002
> |
> 398010.000
> 7541990.000
> 280.436
> |
> 398020.000
> 7541990.000
> 279.847
> |
> |-------------------------------------------------|---------------------------------------------------|-------------------------------------------------|
> 2 |
> 398000.000
> 7541980.000
> 282.096
> |
> 398010.000
> 7541980.000
> 281.539
> |
> 398020.000
> 7541980.000
> 280.944
> |
> |-------------------------------------------------|---------------------------------------------------|-------------------------------------------------|
>
>
> From
> that
> grid
> we
> can
> create
> polygons
> representing
> terrain
> surface.
>
> WKT
> polygons
> generated
> from
> that
> dataset
> should
> look
> like
> this:
> POLYGONZ((398000.000
> 7542000.000
> 279.950,
> 398010.000
> 7542000.000
> 279.388,
> 398010.000
> 7541990.000
> 280.436,
> 398000.000
> 7541990.000
> 281.002,
> 398000.000
> 7542000.000
> 279.950))
> POLYGONZ((398010.000
> 7542000.000
> 279.388,
> 398020.000
> 7542000.000
> 278.818,
> 398020.000
> 7541990.000
> 279.847,
> 398010.000
> 7541990.000
> 280.436,
> 398010.000
> 7542000.000
> 279.388))
> POLYGONZ((398000.000
> 7541990.000
> 281.002,
> 398010.000
> 7541990.000
> 280.436,
> 398010.000
> 7541980.000
> 281.539,
> 398000.000
> 7541980.000
> 282.096,
> 398000.000
> 7541990.000
> 281.002))
> POLYGONZ((398010.000
> 7541990.000
> 280.436,
> 398020.000
> 7541990.000
> 279.847,
> 398020.000
> 7541980.000
> 280.944,
> 398010.000
> 7541980.000
> 281.539,
> 398010.000
> 7541990.000
> 280.436))
>
> NOTE:
> It
> is
> said
> in
> WKT
> specification
> that
> polygons
> needs
> to
> be
> closed,
> meaning
> that
> start
> and
> end
> points
> are
> the
> same.
>
> Each
> polygon
> should
> be
> written
> into
> a PostGIS
> database
> or
> into
> a shape
> file.
>
> - Shapefile
> writing
> can
> be
> done
> for
> example
> with
> python
> library
> called
> pyshp
> (https://github.com/GeospatialPython/pyshp).
>
> - PostGIS
> can
> be
> used
> for
> example
> with
> psycopg2
> library
> (http://initd.org/psycopg/).
>
>
> Depending
> on
> selected
> storage
> format
> choose
> corresponding
> publishing
> steps
> for
> data
> publishing
> into
> a W3DS
> layer
> with
> GeoServer.
> Official
> GeoServer
> guide
> how
> to
> publish
> a shapefile:
>
> - http://docs.geoserver.org/stable/en/user/gettingstarted/shapefile-quickstart/index.html
>
> Official
> GeoServer
> guide
> how
> to
> publish
> a PostGIS
> table:
>
> - http://docs.geoserver.org/stable/en/user/gettingstarted/postgis-quickstart/index.html
>
>
>
> Adding
> texture
>
> Raster
> data
> (f.ex.
> ortophotos)
> is
> used
> as
> terrain
> texture
> and
> guide
> how
> to
> work
> with
> rasters
> can
> be
> found
> from
> here:
> - http://docs.geoserver.org/stable/en/user/data/raster/index.html
>
>
>
> On
> Mon,
> Mar
> 2,
> 2015
> at
> 6:23
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> Thank
> you
> for
> the
> steps.
> However,
> I would
> like
> to
> clarify
> some
> things
> to
> have
> clear
> what
> I should
> do.
> Imagine
> I have
> the
> data:
> lat
> lon
> alt
> 0
>
> 0 0
> 0
>
> 1 5
> 0
>
> 2 10
> 1
>
> 0 5
>
> 1
>
> 1
> 10
> 1
>
> 2
> 15
> 2
>
> 0 10
>
> 2
>
> 1
> 15
> 2
>
> 2
> 20
> This
> is
> like
> a flat
> surface.
> So
> I have
> to
> create
> a 2D
> array
> like:
> 10
> 15
> 20
> 5
> 10
> 15
> 0
> 5
> 10
> I have
> never
> create
> wkt
> polygons
> in
> 3D,
> but
> as
> I have
> seen
> in
> some
> websites,
> this
> could
> be
> done
> like
> this?
> POLYGON
> ((0
> 0 0,
> 0 1
> 5,
> 1 1
> 10,
> 1 0
> 5),
> (0
> 1 5,
> 0 2
> 10,
> 1 1
> 10,
> 1 2
> 15),
> (1
> 0 5,
> 2 0
> 10,
> 1 1
> 10,
> 2 1
> 15),
> (1
> 1 10,
> 1 2
> 15,
> 2 1
> 15,
> 2 2
> 20))
>
> After
> this,
> I am
> not
> sure
> how
> to
> upload
> to
> DDBB
> in
> shp
> because
> I have
> many
> files.
> Also,
> I don't
> know
> how
> to
> associate
> the
> ortophoto
> to
> the
> shapes.
> Being
> honest,
> I am
> a little
> bit
> lost
> and
> I would
> appreciate
> if
> you
> can
> help
> me.
> Thank
> you.
> Kind
> regards,
>
> Ibon
>
>
> 2015-03-02
> 7:38
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> I'm
> sorry
> to
> hear
> that
> you
> still
> have
> those
> problems.
> I'm
> looking
> into
> that
> and
> I will
> report
> back
> to
> you
> if
> I'm
> able
> to
> reproduce
> and
> solve
> it
> in
> some
> environment.
>
> At
> the
> moment
> you
> can't
> use
> .tiff
> file
> format.
>
> Since
> XML3D,
> which
> we
> use
> as
> a rendering
> engine,
> requires
> that
> rendered
> models
> consist
> of
> polygons
> we
> had
> to
> create
> polygonal
> terrain
> from
> .asc
> point
> grid.
> In
> order
> to
> reduce
> processor
> loads
> we
> decided
> that
> data
> should
> be
> stored
> as
> polygons.
> In
> that
> way
> data
> can
> be
> returned
> to
> a client
> without
> any
> further
> processing.
>
> We
> have
> developed
> proprietary
> importing
> tools
> to
> support
> our
> business
> cases
> and
> therefore
> I can't
> provide
> those
> directly
> to
> you
> but
> I can
> describe
> what
> we
> did.
>
> Our
> workflow
> from
> .asc
> files
> included
> three
> steps:
> 1.
> Read
> asc
> file
> and
> create
> 2D
> array
> from
> it
> where
> each
> cell
> is
> a point
> from
> asc
> file
> 2.
> Inside
> a for
> loop
> select
> four
> points
> from
> array
> and
> create
> wkt
> polygon
> from
> those
> points
> 3.
> Write
> just
> created
> polygon
> to
> a database
> or
> to
> a shp
> file
>
> When
> polygons
> are
> stored
> in
> a database
> you
> need
> to
> publish
> that
> table
> in
> GeoServer
> as
> a layer
> and
> configure
> it
> to
> use
> W3DS
> module.
>
> I hope
> that
> this
> clarifies
> needed
> steps
> from
> source
> data
> to
> a production
> use.
>
> - Juha
>
>
> On
> Fri,
> Feb
> 27,
> 2015
> at
> 8:04
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> I continue
> trying
> to
> find
> my
> problem
> but
> I haven't
> advance
> :(
> Anyway,
> I don't
> write
> for
> that.
> I am
> trying
> to
> upload
> xyz
> format
> data
> and
> some
> ortophotos
> to
> display
> them
> with
> W3DS.
> I have
> the
> data
> in
> *.asc
> files
> and
> I have
> a TIF
> file
> with
> all
> of
> them
> merged.
> As
> the
> documentation
> (https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_User_and_Programmers_Guide)
> says
> that
> the
> /.shp,
> .dbf/ and
> /.shx/files
> are
> mandatory,
> I should
> convert
> all
> /.asc/
> to
> these
> formats?
> I cannot
> use/.tif/?
> As
> the
> documentation
> syas,
> I have
> to
> upload
> this
> files
> to
> the
> server
> and
> I suppose
> that
> the
> ortophotos
> also.
> However,
> I don't
> know
> how
> to
> display
> them
> afterwards.
> Can
> you
> explain
> me?
> I am
> in
> a Fiware
> European
> project
> and
> as
> you
> are
> the
> support
> of
> Fiware
> I hope
> you
> can
> help
> me.
> Thank
> you.
> Best
> regards,
>
> Ibon
>
> 2015-02-24
> 11:58
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> I have
> no
> glue
> why
> it's
> not
> loading
> since
> personally
> I haven't
> ever
> used
> that
> module.
> You
> should
> read
> GeoServer
> startup
> logs
> and
> check
> if
> there
> are
> some
> fatal
> errors
> in
> service
> loading.
> Logs
> should
> have
> something
> similar
> lines
> to
> these:
> 24
> Feb
> 13:53:03
> INFO
> [org.geoserver]
> - Loaded
> service
> 'wfs',
> enabled
> 24
> Feb
> 13:53:03
> INFO
> [org.geoserver]
> - Loaded
> service
> 'wms',
> enabled
> 24
> Feb
> 13:53:03
> INFO
> [org.geoserver]
> - Loaded
> service
> 'wcs',
> enabled
> 24
> Feb
> 13:53:03
> INFO
> [org.geoserver]
> - Loaded
> service
> 'w3ds',
> enabled
>
> Check
> errors
> near
> those.
>
> There
> is
> also
> GeoServer
> users
> mail
> list
> and
> you
> probably
> could
> get
> more
> helpful
> response
> from
> there,
> since
> I'm
> not
> expert
> in
> that
> area.
>
> On
> Tue,
> Feb
> 24,
> 2015
> at
> 1:13
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> Thank
> you
> for
> the
> comments.
> About
> the
> "Importer
> extension"
> I downloaded
> the
> core
> extension
> for
> version
> 2.6.0
> as
> you
> said
> because
> I show
> that
> was
> the
> version
> when
> I install
> it.
> So,
> can
> you
> guess
> the
> reason
> of
> the
> extension
> for
> not
> working.
> As
> you
> explained,
> W3DS
> is
> an
> isolated
> module,
> so
> it
> has
> no
> sense
> for
> not
> working.
> Kind
> regards,
>
> Ibon
>
> 2015-02-24
> 11:08
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> Changes
> delivered
> to
> FIWARE
> are
> isolated
> only
> to
> W3DS
> module
> and
> those
> are
> written
> on
> top
> of
> the
> GeoServer
> version
> 2.6.0.
> Therefore
> you
> need
> to
> use
> extensions
> written
> for
> that
> specific
> version.
> We
> will
> move
> to
> next
> stable
> version
> 2.7
> when
> it
> is
> released
> later
> this
> spring.
> Currently
> 2.7
> release
> is
> in
> RC1
> state.
>
> Our
> changes
> are
> also
> in
> the
> official
> GeoServer
> master
> and
> 2.7
> branches
> and
> you
> could
> actually
> try
> to
> build
> either
> of
> those
> and
> see
> if
> build
> problem
> still
> exists.
> Meanwhile
> I try
> to
> replicate
> your
> problem
> in
> a virtual
> machine
> since
> everything
> worked
> well
> in
> every
> physical
> machines
> I have
> access
> to.
>
> On
> Tue,
> Feb
> 24,
> 2015
> at
> 11:13
> AM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> I continue
> having
> a failure
> message
> in
> the
> same
> test.
> I have
> continued
> looking
> to
> the
> builded
> version
> (without
> tests
> as
> I said)
> and
> I was
> trying
> to
> use
> the
> "Importer
> extension"
> installed
> by
> copying
> some
> source
> from
> this
> link:
> http://docs.geoserver.org/latest/en/user/extensions/importer/installing.html
> I copied
> the
> files
> to
> the
> folder
> ".../geoserver/src/web/app/target/geoserver/WEB-INF/lib"
> as
> it
> says
> and
> restart
> Geoserver,
> but
> the
> extension
> does
> not
> seems
> to
> load.
> Could
> be
> due
> to
> the
> Geoserver
> version
> done
> for
> fiware?
> Or,
> how
> could
> I solve
> the
> problem?
> Thank
> you.
> Kind
> regards,
>
> Ibon
>
> 2015-02-23
> 11:55
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> Only
> difference
> between
> our
> work
> chains
> that
> I was
> able
> to
> find
> is
> that
> I use
> also
> clean
> statement
> in
> mvn
> build
> command.
> Could
> you
> try
> that?
> If
> it's
> still
> not
> working
> I try
> to
> find
> some
> time
> to
> reproduce
> problem
> in
> a clean
> machine.
>
> mvn
> clean
> install
> -DdownloadSources=true
> -DskipTests=false
> -Pw3ds
>
> Resulting
> following
> summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> Reactor
> Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> GeoServer
> .............................................
> SUCCESS
> [2.088s]
> [INFO]
> Core
> Platform
> Module
> ..................................
> SUCCESS
> [9.062s]
> [INFO]
> Open
> Web
> Service
> Module
> ...............................
> SUCCESS
> [5.411s]
> [INFO]
> Main
> Module
> ...........................................
> SUCCESS
> [1:58.712s]
> [INFO]
> GeoServer
> Security
> Modules
> ............................
> SUCCESS
> [0.043s]
> [INFO]
> GeoServer
> JDBC
> Security
> Module
> ........................
> SUCCESS
> [18.349s]
> [INFO]
> GeoServer
> LDAP
> Security
> Module
> ........................
> SUCCESS
> [35.825s]
> [INFO]
> Web
> Coverage
> Service
> Module
> ...........................
> SUCCESS
> [1.450s]
> [INFO]
> Web
> Coverage
> Service
> 1.0
> Module
> .......................
> SUCCESS
> [18.896s]
> [INFO]
> Web
> Coverage
> Service
> 1.1
> Module
> .......................
> SUCCESS
> [19.249s]
> [INFO]
> Web
> Coverage
> Service
> 2.0
> Module
> .......................
> SUCCESS
> [46.273s]
> [INFO]
> Web
> Feature
> Service
> Module
> ............................
> SUCCESS
> [1:21.581s]
> [INFO]
> Web
> Map
> Service
> Module
> ................................
> SUCCESS
> [1:27.636s]
> [INFO]
> KML
> support
> for
> GeoServer
> .............................
> SUCCESS
> [24.646s]
> [INFO]
> GeoWebCache
> (GWC)
> Module
> ..............................
> SUCCESS
> [55.551s]
> [INFO]
> REST
> Support
> Module
> ...................................
> SUCCESS
> [10.524s]
> [INFO]
> REST
> Configuration
> Service
> Module
> .....................
> SUCCESS
> [54.318s]
> [INFO]
> GeoServer
> Web
> Modules
> .................................
> SUCCESS
> [0.028s]
> [INFO]
> Core
> UI
> Module
> ........................................
> SUCCESS
> [46.005s]
> [INFO]
> WMS
> UI
> Module
> .........................................
> SUCCESS
> [17.764s]
> [INFO]
> GWC
> UI
> Module
> .........................................
> SUCCESS
> [23.123s]
> [INFO]
> WFS
> UI
> Module
> .........................................
> SUCCESS
> [10.234s]
> [INFO]
> Demoes
> Module
> .........................................
> SUCCESS
> [16.390s]
> [INFO]
> WCS
> UI
> Module
> .........................................
> SUCCESS
> [12.849s]
> [INFO]
> Security
> UI
> Modules
> ...................................
> SUCCESS
> [0.037s]
> [INFO]
> Security
> UI
> Core
> Module
> ...............................
> SUCCESS
> [1:14.168s]
> [INFO]
> Security
> UI
> JDBC
> Module
> ...............................
> SUCCESS
> [50.839s]
> [INFO]
> Security
> UI
> LDAP
> Module
> ...............................
> SUCCESS
> [27.079s]
> [INFO]
> REST
> UI
> Module
> ........................................
> SUCCESS
> [10.953s]
> [INFO]
> Community
> Space
> .......................................
> SUCCESS
> [0.027s]
> [INFO]
> Web
> 3D
> Service
> ........................................
> SUCCESS
> [4.663s]
> [INFO]
> GeoServer
> Web
> Application
> .............................
> SUCCESS
> [3.207s]
> [INFO]
> GeoServer
> Extensions
> ..................................
> SUCCESS
> [0.083s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> BUILD
> SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> Total
> time:
> 14
> minutes
> 49
> seconds
> [INFO]
> Finished
> at:
> Mon
> Feb
> 23
> 13:26:42
> EET
> 2015
> [INFO]
> Final
> Memory:
> 187M/1400M
> [INFO]
> ------------------------------------------------------------------------
>
> On
> Mon,
> Feb
> 23,
> 2015
> at
> 12:33
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com
> <mailto:ibon.salbi at gmail.com>>
> wrote:
>
> Hi
> Juha,
>
>
> I followed
> the
> installation
> guide
> of
> Fiware
> for
> installation.
> I used
> a Ubuntu
> 14.04
> Server
> 64
> bits
> with
> 4 cores,
> 8GB
> RAM
> and
> 100GB
> of
> HD.
> The
> version
> of
> JDK
> (openjdk-7-jdk)
> is 7u51-2.4.6-1ubuntu4,
> and
> postgis 2.1.0
> The
> source
> that
> I downloaded
> is
> the
> one
> you
> shared
> from
> git
> (git
> clone
> -b
> fiware
> https://github.com/Cyberlightning/geoserver.git)
> I followed
> all
> the
> commands
> so
> that's
> the
> reason
> from
> asking.
> I would
> appreciate
> if
> you
> can
> tell
> me
> what
> can
> be
> different.
> Thank
> you.
> Kind
> regards,
>
> Ibon
>
> 2015-02-20
> 13:03
> GMT+00:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>>:
>
> Hi
> Ibon,
>
>
> without
> knowledge
> about
> your
> build
> system
> (used
> java
> version,
> used
> operating
> system
> etc.)
> and
> where
> you
> downloaded
> sources
> I'm
> not
> able
> to
> help
> you
> with
> this
> problem.
> I just
> tested
> version
> which
> we
> have
> delivered
> to
> FIWARE
> (https://github.com/Cyberlightning/geoserver/tree/fiware)
> and
> at
> least
> it
> build
> without
> any
> errors
> in
> any
> test
> cases.
>
> Also,
> CatalogBuilder
> is
> bit
> out
> of
> my
> knowledge
> scope.
>
>
>
> On
> Fri,
> Feb
> 20,
> 2015
> at
> 1:18
> PM,
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com>
> wrote:
>
>
> Sorry,
> I forget
> to
> attach
> the
> log.
>
> 2015-02-20
> 11:17
> GMT+00:00
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com>:Hi
> Juha,I
> have
> one
> comment
> about
> the
> installation.
> Previously
> when
> I installed
> the
> geoserver
> I didn't
> notice
> because
> I was
> building
> without
> tests.But
> I was
> building
> geoserver
> with
> test
> where
> I found
> a failure
> on:testSingleBandedCoverage(org.geoserver.catalog.impl.CatalogBuilderTest)I
> attached
> the
> log
> of
> the
> output
> for
> your
> information.How
> can
> I solve
> this
> problem?Thank
> you
> in
> advance.
> Kind
> regards,Ibon2015-02-05
> 7:48
> GMT+00:00
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com>:Hi
> Juha,Thank
> you
> for
> the
> reply.I
> have
> a xyz
> format
> data
> also
> so
> I will
> try
> to
> test
> what
> you
> sent
> me
> and
> look
> for
> the
> Unit
> Testing
> Plan
> link
> you
> sent.If
> I have
> any
> doubt
> or
> problem
> I will
> come
> back
> to
> you.
> Thank
> you.Kind
> regards,Ibon2015-02-05
> 7:27
> GMT+01:00
> Juha
> Hyvärinen
> <juha.hyvarinen at cyberlightning.com>:Hi
> Ibon,Data
> publishing
> is
> well
> documented
> in
> GeoServer
> user
> manual: http://docs.geoserver.org/2.5.x/en/user/Data
> which
> we
> used
> in
> our
> development
> was
> from National
> Land
> Survey
> of
> Finland.
> Source
> data
> was
> in -xyz-format,
> which
> contains
> elevation
> data
> with
> spatial
> information.
> With
> this
> source
> information
> it
> is
> possible
> to
> generate
> shapefile
> consisting
> polygon
> structure
> with
> elevation
> data.
> 2D
> presentation
> of
> the
> converted
> shapefile
> with
> elevation
> points
> is
> flat
> grid,
> in
> 3D
> presentation
> each
> grid
> points
> are
> in
> same
> elevation
> level
> as
> in
> the
> real
> world.
> Therefore
> this
> grid
> with
> elevation
> data
> can
> be
> used
> as
> source
> for
> terrain
> presentation.You
> can
> also
> read
> user
> guide
> from:https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_User_and_Programmers_GuideYou
> can
> find
> guide
> for
> setting
> up
> test
> setup
> from
> here: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_Unit_Testing_Plan-
> Juha----------
> Forwarded
> message
> ----------From:
> Ibon
> Salbidegoitia
> <ibon.salbi at gmail.com>Date:
> Wed,
> Feb
> 4,
> 2015
> at
> 12:35
> AMSubject:
> W3DS
> - FIWARETo:
> miika.santala at cyberlightning.comDear
> Miika,I
> am
> Ibon
> from
> Spain.I
> write
> to
> you
> because
> I am
> involved
> in
> the
> FIWARE
> European
> project.
> This
> project
> promote
> a GIS
> data
> provider
> with
> the
> W3DS
> for
> 3D
> visualization
> as
> the
> one
> you
> show
> on
> the
> following
> link:http://130.206.81.238:8080/gis_test_client/index.xhtmlI
> contact
> you
> because
> a have
> been
> in
> contact
> with
> Jorge
> Gustavo,
> who
> made
> a similar
> use
> of
> W3DS
> (http://www.sigte.udg.edu/jornadassiglibre2012/uploads/presentaciones_12/p43.pdf)
> and
> he
> told
> me
> that
> W3DS
> is
> now
> supported
> by
> you.I
> have
> followed
> the
> instructions
> of
> FIWARE
> wiki
> (https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/GIS_Data_Provider_-_Installation_and_Administration_Guide)
> to
> start
> using
> the
> service
> and
> everything
> seems
> to
> work
> perfectly
> with
> Jetty.However,
> I would
> like
> to
> know
> how
> I have
> to store
> GIS
> data
> with
> 3D
> information
> straight
> to
> GeoServer.
> Is
> there
> any
> documentation
> of
> how
> to
> upload
> this
> kind
> of
> information?
> Can
> you
> share
> with
> me
> any
> documentation
> about
> it?Thank
> you
> in
> advance.
> Yours
> sincerely,Ibon
> --
> Juha
> HyvärinenSoftware
> EngineerCyberlightning
> Ltd.email.
> juha.hyvarinen at cyberlightning.comSee
> our
> new
> press
> release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/www.cyberlightning.comThis
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
> email.
> juha.hyvarinen at cyberlightning.com
> See
> our
> new
> press
> release: http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
> www.cyberlightning.com
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
>
> --
>
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See
> our
> new
> press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and
> all
> attached
> material
> are
> confidential
> and
> may
> contain
> legally
> privileged
> information.
> If
> you
> are
> not
> the
> intended
> recipient,
> please
> contact
> the
> sender
> and
> delete
> the
> e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
>
>
>
> --
> Juha
> Hyvärinen
> Software
> Engineer
> Cyberlightning
> Ltd.
>
> email.
> juha.hyvarinen at cyberlightning.com
> <mailto:juha.hyvarinen at cyberlightning.com>
>
> See our
> new press
> release:
> http://cyberlightning.com/blog/2014/05/13/cyberlightning-brings-3d-visualization-to-industrial-internet-of-things/
>
> www.cyberlightning.com
> <http://www.cyberlightning.com/>
>
> This
> e-mail
> and all
> attached
> material
> are confidential
> and may
> contain
> legally
> privileged
> information.
> If
> you are
> not the
> intended
> recipient,
> please
> contact
> the sender
> and delete
> the e-mail
> from
> your
> system
> without
> producing,
> distributing
> or
> retaining
> copies
> thereof.
>
> ...
>
> [Mensaje recortado]
>
>
>
>
>
> _______________________________________________
> Fiware-finodex-coaching mailing list
> Fiware-finodex-coaching at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-finodex-coaching
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-finodex-coaching/attachments/20150714/edac13fb/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy