Bill Dollins wrote an excellent paean to the positive aspects of vendor lock-in, which is worth a few minutes of your time:

Lock-in is a real thing. Lock-in can also be a responsible thing. The organizations I have worked with that make the most effective use of their technology choices are the ones that jump in with both feet and never look back. They develop workflows around their systems; they develop customizations and automation tools to streamline repetitive tasks and embed these in their technology platforms; they send their staff to beginning and advanced training from the vendor; and they document their custom tools well and train their staff on them as well. In short, they lock themselves in.

I think locking yourself into a good technology could have all the positive knock-on effects Bill lists. But, we never quite know what we're getting, good or bad, until we've spent some time with it. Which to me means being carefully modular and standards-oriented in design (which is to say, the opposite of how most vendors will architect a solution).

The BC Integrated Case Management (ICM) project yet again provides an excellent example of the negative aspects of vendor worship. In this case, ICM chose their software vendor first (way back in the single-digit 2000's they chose Seibel) and then chose their system integrator (Deloitte) and finally began to get the first major phases of delivery a couple years ago. One result of this slow motion train wreck is that the Seibel software is dragging other aspects of the Ministry's technology base down to its level.

For example, among the limitations (scroll to the bottom) ICM (Seibel) imposes are:

• "Using any version of IE other than IE 8 may result in unexpected behavior". So no IE 9, 10, or 11. Also, no Windows 8 support, since IE 8 only works on Windows 7 or less. Also no browser other than IE.
• "The 32-bit ActiveX Seibel plug-in does not work with 64-bit IE". So all sorts of potential collisions between 64-bit/32-bit libraries. (The sysadmins weep.)

Only a few years after launch, ICM is already locking the Ministry to desktop technology that is several versions out of date, which will in turn restrict flexibility for doing more modern work in the future. This is one of the the downsides of lock-in.

OpenGeo Suite is a complete geospatial platform for managing data and building maps and applications. In the newest version, Boundless makes it even easier to build and deploy applications by adding better data management tools to QGIS and improving the SDK with support for OpenLayers 3.

This post is the first of a series of posts describing how to create complete, enterprise-grade web applications using these and other features. While we’ve previously shown how to configure OpenGeo Suite from QGIS, this post will describe a typical workflow to show how easy it is to analyze and style on the desktop using QGIS and then publish to the web using GeoServer. Our next post will describe how to use this data to create an application to visualize this data.

Our first demo application, Ice³, is a mapping application that visualizes changes in Arctic sea ice over a 33 year period (1980-2013). The maximum August sea ice extent is shown in the timeline slider beneath the map. Additionally, an outline of the 30-year (1981-2010) median August sea ice extent is included for comparison. All data is from the National Snow & Ice Data Center, a source for consistently processed ice extent and concentration images and data values since 1979. A third dataset showing the average snow extent in August (1967-2004) is also included for reference.

Preparing the Data

The workflow that we have to execute involves loading and reprojecting several layers into the same coordinate reference system (CRS), styling them, and then publishing them to GeoServer. It is not strictly necessary to reproject layers, as GeoServer can do that on the fly, but if we expect most requests to use a given CRS then reprojecting them in advance will avoid having to reproject them at request time and thus make our service more performant.  In order to show the capabilities of GeoServer, other posts in this series will use layers in their original CRS, but in this one we will be reprojecting them to a common one using QGIS. We will be using the following datasets:

• Natural Earth
  • Base map
  • EPSG 4326
• Sea Ice Index (August)
  • Median (1981-2010) polyline
  • Extent (1980-2013 every 3 years) polygons, 12 data layers
  • Shapefiles from University of Colorado Boulder
  • EPSG 3413
• Atlas of the Cryosphere
  • Average Snow Extent in August (1967-2004)
  • WMS Connection
  • EPSG:3408

Setting up GeoServer

Before preparing our layers, we need configure the GeoServer catalog. From the QGIS plugin, we can connect to our GeoServer instance and create a new workspace that will contain our layers.

Base map layer

To reproject the Natural Earth base map layer into a polar projection, we will use the Reproject vector layer algorithm in the Processing toolbox. Doing so will generate a new layer in the EPSG:3408 CRS, which will be our target for all layers.

We can then define a style for the layer on the layer properties dialog. Once the layer is ready to be published,  we can drag and drop the layer into the desired catalog and workspace using the QGIS plugin.

Average snow extent layer

The average snow extent layer is based on an an existing WMS service. Currently, cascading a WMS service can only be configured from the GeoServer administration interface, but an upcoming release of OpenGeo Suite will make it possible to define a new connection in QGIS…

…and then add a corresponding layer from the list provided by that service.

Sea ice layers

Preparing and publishing the sea ice layers is the most complex part, since there is a large number of them. We will show how to automate the process to simplify it.

All layers will have the same styling, since we do not plan to show them together, but as different snapshots. That means we can reuse the style definition. We style one of the layers and then save the style as a QGIS QML file.

The operation that we need to perform for all the layers in the sea ice set is reprojecting them and then applying the style that we have just saved. To make it easier to run repeatedly, we can define this small workflow as a model in the QGIS processing framework. This is what the model should look like:

The reprojection algorithm uses EPSG:3408 as the destination CRS, and the Style vector layer algorithm uses our QML style file.

To run this model in all of our layers, we can run it as a batch process. Selecting the sea ice layers as inputs for the batch process will generate a new set of reprojected and styled layers, ready to be published to GeoServer.

Another way of using our model is by setting it as a pre-publish hook. Our QGIS plugin makes it possible to define an operation to be performed to any layer as it is published. If we set our model to run when publishing then there is no need to run the batch process. Simply publish the set of sea ice layer from our QGIS plugin by dragging and dropping them on the destination workspace item they will be reprojected and styled as they’re published.

Preparing the cache

Once all layers are published, we can also create the corresponding cache layers and seed the cache from the QGIS plugin. To create a cache layer, just right-click on the GeoWebCache item and select the GWC layer and then specify the layer to cache.

Or, even easier, just drag a Geoserver layer into the GeoWebCache item. You can then cache the layer to its full extent, or, if you just want to cache a given region, define its bounding box by clicking on Define in canvas button and then dragging and dropping the QGIS map to select the bounding box.

Conclusion

Now we have configured all the layers for our Ice³ demo application by reprojecting and publishing from QGIS to GeoServer.  In the next post we will see how to use the OpenGeo Suite SDK to create an interface for the application using OpenLayers 3.

The post Ice Cubed (Part 1): Data Preparation with QGIS appeared first on Boundless.

• Have a list of hack ideas (by participants who actually have some ideas) up some time before the hackathon starts. This would facilitate team building, letting participants with the skills, but without ideas easily gravitate towards people/teams with the ideas.
• The mandatory video requirement for each hack entry just doesn't work in its current form. Asking teams to produce their own videos puts lots of unnecessary stress on teams, who not only have to come up with the content for their video, but have to also deal with the logistics of producing said video. I would strongly prefer that teams who can/want to make their own video do so, while other teams can just do a <= 3 minute presentation and have that be recorded by the GovHack organisers. Presentations also lets teams find out how other teams fared over the weekend. While everyone else in the ThoughtWorks Melbourne office was counting down to the end of the hackathon, I was still frantically trying to record my lines and trying not to flub them! I raided the office fridge for whatever free booze that remained just to calm myself down afterwards. I don't want to be in that situation ever again!
• Finally, the data itself. So many "spatial" datasets as CSV files! So many datasets with no coordinates, but have addresses, horribly formatted addresses, adding even more hoops to geocode them. KML/KMZ may be a decent consumer format, but it is a terrible data source format. If ogr2ogr can't convert your dataset, and requires a manual intervention of QGIS to fix it, then perhaps it's better to use a different spatial data format. Despite my loathing of its limitations, SHP files would've been heavily preferred for all of the above cases. I've made my thoughts known on the GovHack DataRater about the quality of some of these datasets we had to deal with and got plenty of imaginary ponies in the process.

PosGIS Viewer 3D suite

ntroduction

Comme je vous l’annoncez dans mon précédent billet j’ai fait évoluer le pg3DViewer pour qu’il puisse gérer les géométries de type POINT, et pour mes test je me suis intéressé aux nuages de points ‘Points Clouds’'

Pour la suite de ce tutorial nous utiliserons deux fichiers de données dont voici les liens de téléchargement :

• un fichier Ascii au format xyz : bunny.xyz
• un fichier de données LIDAR sur le site City Of Surrey :http://media.surrey.ca/files/opendata/2013%20LiDAR%205105_54480.las

nstallation

Cliquez sur le lien pg3DViewer_setup.exe pour télécharger le programme d’installation de la nouvelle version, si vous aviez installé la version précédente désinstallez la, puis lancer l’exécution. Cliquer sur le  bouton Suivant à chaque étape, puis sur le bouton Terminer.

Dans le précédent billet vous avez tous les écrans de l’installation : http://ageoguy.blogspot.fr/2014/07/postgis-3d-viewer.html

tilisation

Avant de commencer à utiliser pg3Dviewer vous devez avoir une base de données PostgreSQL avec la cartouche spatiale PostGIS version 2.0 ou supérieure.

Double cliquez sur l’icone créé par le programme d’installation sur le bureau pour lancer l’application.

Connecter vous à votre base de données 3D

	Commencez par cliquer sur cet icône pour vous connecter a une base de données PostgreSQL/PostGIS version 2.0 ou supérieur contenant des données 3D ou prête à en recevoir.
	Choisissez localhost pour serveur si votre base de données est en local sur votre machine ou bien saisissez l’adresse IP de votre serveur le port est par défaut 5432, changez le si nécessaire saisissez l’utilisateur saisissez le mot de passe choisissez une base de donnée dans la combobox cliquez sur le bout OK pour valider votre saisie.

Traitement d’un fichier Ascii XYZ

Nous allons utiliser le fichier bunny.xyz que vous avez téléchargé dans l’introduction.

Nous allons créer la table qui va accueillir les donnés. Dans PgAdmin III ouvrez l’outil de requêtes puis copiez la requête suivante : -- Table: bunny -- DROP TABLE bunny; CREATE TABLE bunny (   x double precision,   y double precision,   z double precision,   id bigserial NOT NULL,   CONSTRAINT bunny_pkey PRIMARY KEY (id) ) WITH (   OIDS=FALSE ); ALTER TABLE bunny   OWNER TO postgres; Puis exécuter la.
Puis nous allons insérer les données dans la table. Copiez la requête suivante dans l’éditeur de requêtes : copy lidar_test(x,y,z,classification) from 'C:/temp/bunny.txt' with delimiter ' ' puis exécuter la.
Maintenant nous allons pouvoir visualiser les données. Dans le panneau Query copiez la requête suivante : SELECT x,y,z FROM bunny AS points_xyz Cliquez sur l’icone ‘Execute query’
Et voici le résultat après Zoom et Rotation. Comme vous avez du le remarquer le temps d’affichage est très rapide pour une table contenant 34835 points.
Nous allons maintenant essayer une nouvelle requête.Dans le panneau Query copiez la requête suivante : SELECT st_geomfromtext('POINT Z('||x||' '||y||' '||z||')',0) as geom,'255:0:0'::text AS rgb FROM bunny Cliquez sur l’icone ‘Execute query’
Et voici le résultat après Zoom et Rotation. Le temps d’affichage est beaucoup plus long parce que dans cette requête nous construisons la géométrie à la volée. La différence avec la requête précédente est que celle-ci génère un fichier de points au format xyz (grâce à la commande COPY TO de PostgreSQL) qu’exploite un ‘reader’ de  la bibliothèque VTK. Tout cela ce fait avec l’ajout de ‘A'S points_xyz’ a la fin de la requête et la sélection des champs x,y et z.

Traitement d’un fichier LAS

Ouvrez une fenêtre DOS, allez dans le répertoire ou vous avez installé LASTOOLS, puis dans le sous répertoire bin. Copiez la commande suivante : las2txt -i "C:\temp\2013 LiDAR 5105_54480.las" -parse xyzc -sep semicolon Cette commande va générer un fichier Ascii (.txt) au format x,y,z et classification avec pour séparateur de colonne le caractère ‘;’ (point virgule).
Nous disposons à présent d’un fichier que nous allons pouvoir insérer dans notre base de données. Pour cela nous allons commencer par créer la table qui recevra les données, dans la fenêtre de requêtes de PgAdmin III copiez la requête suivante: -- Table: lidar_test -- DROP TABLE lidar_test; CREATE TABLE lidar_test (   x double precision,   y double precision,   z double precision,   classification integer ) WITH (   OIDS=FALSE ); ALTER TABLE lidar_test   OWNER TO postgres; puis exécuter la.
Puis nous allons insérer les données dans la table. Copiez la requête suivante dans l’éditeur de requêtes : copy lidar_test(x,y,z,classification) from 'C:/temp/2013 LiDAR 5105_54480.txt' with delimiter ';' puis exécuter la.
Maintenant nous allons pouvoir visualiser les données. Dans le panneau Query copiez la requête suivante : select x,y,z, CASE WHEN classification=2 then '128:0:0' WHEN classification=3 then '0:64:0' WHEN classification=4 then '0:128:0' WHEN classification=5 then '0:255:0' WHEN classification=6 then '255:128:64' WHEN classification=11 then '128:128:128' END as rgb from lidar_test as points_xyzrgb Cliquez sur l’icone ‘Execute query’
Et voici le résultat
Les valeurs de classification utilisées dans la requête sont issues de cette requête : select distinct classification from lidar_test order by 1 Vous pouvez également obtenir des informations sur le fichier LAS avec l’outil lasinfo, dans une fenêtre DOS tapez la commande suivante : lasinfo c:\temp\2013 LiDAR 5105_54480.las a la fin du rapport vous obtenez la définition de la classification.	lasinfo for c:\temp\2013 LiDAR 5105_54480.las reporting all LAS header entries:   file signature:             'LASF'   file source ID:             0   global_encoding:            1   project ID GUID data 1-4:   00000000-0000-0000-0000-000000000000   version major.minor:        1.2   system identifier:          ''   generating software:        'TerraScan'   file creation day/year:     156/2013   header size:                227   offset to point data:       447   number var. length records: 2   point data format:          1   point data record length:   28   number of point records:    7938187   number of points by return: 6742290 914660 231891 44542 4804   scale factor x y z:         0.001 0.001 0.001   offset x y z:               510499.94 5447999.8799999999 0   min x y z:                  510499.940 5447999.880 34.110   max x y z:                  511000.110 5448500.100 275.690 variable length header record 1 of 2:   reserved             43707   user ID              'LASF_Projection'   record ID            34735   length after header  88   description          'Georeferencing Information'     GeoKeyDirectoryTag version 1.1.0 number of keys 10       key 1024 tiff_tag_location 0 count 1 value_offset 1 - GTModelTypeGeoKey: ModelTypeProjected       key 2048 tiff_tag_location 0 count 1 value_offset 4269 - GeographicTypeGeoKey: GCS_NAD83       key 2054 tiff_tag_location 0 count 1 value_offset 9102 - GeogAngularUnitsGeoKey: Angular_Degree       key 2056 tiff_tag_location 0 count 1 value_offset 7019 - GeogEllipsoidGeoKey: Ellipse_GRS_1980       key 2057 tiff_tag_location 34736 count 1 value_offset 0 - GeogSemiMajorAxisGeoKey: 6378137       key 2058 tiff_tag_location 34736 count 1 value_offset 1 - GeogSemiMinorAxisGeoKey: 6356752.314       key 2059 tiff_tag_location 34736 count 1 value_offset 2 - GeogInvFlatteningGeoKey: 298.2572221       key 3072 tiff_tag_location 0 count 1 value_offset 26910 - ProjectedCSTypeGeoKey: UTM 10 northern hemisphere       key 3076 tiff_tag_location 0 count 1 value_offset 9001 - ProjLinearUnitsGeoKey: Linear_Meter       key 4099 tiff_tag_location 0 count 1 value_offset 9001 - VerticalUnitsGeoKey: Linear_Meter variable length header record 2 of 2:   reserved             43707   user ID              'LASF_Projection'   record ID            34736   length after header  24   description          'Double Param Array'     GeoDoubleParamsTag (number of doubles 3)       6.37814e+006 6.35675e+006 298.257 reporting minimum and maximum for all LAS point record entries ...   X                   0     500170   Y                   0     500220   Z               34110     275690   intensity           0        255   return_number       1          5   number_of_returns   1          5   edge_of_flight_line 0          0   scan_direction_flag 0          1   classification      2         11   scan_angle_rank   -19         22   user_data          79         79   point_source_ID 10217      10238   gps_time 49786940.848411 49796462.877692 WARNING: there is coordinate resolution fluff (x10) in XYZ overview over number of returns of given pulse: 5825940 1363444 563503 160908 24392 0 0 histogram of classification of points:          2030423  ground (2)          1836807  low vegetation (3)           234836  medium vegetation (4)          1811842  high vegetation (5)          2022021  building (6)             2258  road surface (11)

onclusion.

Nous sommes arrivés à la fin de ce billet, je vous conseille la lecture d’un excellent tutorial de Paul Ramsey concernant les données LIDAR que vous trouverez a cette adresse  http://workshops.boundlessgeo.com/tutorial-lidar/ , il ne vous restera plus qu’a afficher les données en utilisant les fonctions présentées dans ce ‘tutorial lidar’.

1. Testing to verify everything works in this new system and fixing bugs. Download alpha1 here [0].
2. Updating version number in your Project Overview (if changed), and possibly mention a new feature or two. Doc howtos [4].
3. Re-running the Quickstart and ensure each step is still valid, and screenshots match the implementation.
4. Updating status of the Project Overview and Quickstart to "8.0draft" in our status sheet. [1]

Schedule

• 27 July 2014 Alpha4 released [3]. Please verify all applications work and fix bugs.
• 03 August 2014 Beta1 release - start taking screen shots with new background.
• 07 August 2014 Community Testing Sprint (UAT).
• 07 August 2014 English docs complete.
• 14 August 2014 Translations complete.
• 17 August 2014 OSGeo-Live 8.0 sent to the printers.

Last year (2013) I “enjoyed” a brain CT scan in order to identify a post-surgery issue – luckily nothing found. Being in Italy, like all patients I received a CD-ROM with the scan data on it: so, something to play with! In this article I’ll show how to easily turn 2D scan data into a volumetric (voxel) visualization.

The CT scan data come in a DICOM format which ImageMagick is able to read and convert. Knowing that, we furthermore need the open source software packages GRASS GIS 7 and Paraview to get the job done.

First of all, we create a new XY (unprojected) GRASS location to import the data into:

# create a new, empty location (or use the Location wizard):
grass70 -c ~/grassdata/brain_ct

We now start GRASS GIS 7 with that location. After mounting the CD-ROM we navigate into the image directory therein. The directory name depends on the type of CT scanner which was used in the hospital. The file name suffix may be .IMA.

Now we count the number of images, convert and import them into GRASS GIS:

# list and count
LIST=`ls -1 *.IMA`
MAX=`echo $LIST | wc -w`

# import into XY location:
curr=1
for i in $LIST ; do

# pretty print the numbers to 000X for easier looping:
curr=`echo $curr | awk ‘{printf “%04d\n”, $1}’`
convert “$i” brain.$curr.png
r.in.gdal in=brain.$curr.png out=brain.$curr
r.null brain.$curr setnull=0
rm -f brain.$curr.png
curr=`expr $curr + 1`

done

At this point all CT slices are imported in an ordered way. For extra fun, we can animate the 2D slices in g.gui.animation:

(click to enlarge)

# enter in one line:
g.gui.animation rast=`g.mlist -e rast separator=comma pattern=”brain*”`

The tool allows to export as animated GIF or AVI:

(click to enlarge)

Now it is time to generate a volume:

# first count number of available layers
g.mlist rast pat=”brain*” | wc -l

# now set 3D region to number of available layers (as number of depths)
g.region rast=brain.0003 b=1 t=$MAX -p3

At this point the computational region is properly defined to our 3D raster space. Time to convert the 2D slices into voxels by stacking them on top of each other:

# convert 2D slices to 3D slices:
r.to.rast3 `g.mlist rast pat=”brain*” sep=,` out=brain_vol

We can now look at the volume with GRASS GIS’ wxNVIZ or preferably the extremely powerful Paraview. The latter requires an export of the volume to VTK format:

# fetch some environment variables
eval `g.gisenv -s`
# export GRASS voxels to VTK 3D as 3D points, with scaled z values:
SCALE=2
g.message “Exporting to VTK format, scale factor: $SCALE”
r3.out.vtk brain_vol dp=2 elevscale=$SCALE \
output=${PREFIX}_${MAPSET}_brain_vol_scaled${SCALE}.vtk -p

Eventually we can open this new VTK file in Paraview for visual exploration:

# show as volume
# In Paraview: Properties: Apply; Display Repres: volume; etc.
paraview –data=brain_s1_vol_scaled2.vtk

Fairly easy!

BTW: I have a scan of my non-smoker lungs as well

The post Rendering a brain CT scan in 3D with GRASS GIS 7 appeared first on GFOSS Blog | GRASS GIS Courses.

Back in March we had a Save the Date post for FOSS4G 2014 in Portland. Check your travel plans include participating in the Code Sprint at the end of the conference.

The code sprint is an opportunity for the team to get together and work on “tough problems without funding”. For GeoServer we have two candidates:

1. Update to a recent version of Wicket to improve browser compatibility
2. Update CITE Conformance Tests

GeoServer is extending the code sprint to include:

• Saturday, September 13th: FOSS4G is providing facilities at WhereCampPDX.
• Sunday, September 14th: Boundless is arranging facilities at nedspace from 10am-4pm.

To attend add your name to OSGeo wiki page and we will look forward to seeing you in Portland!

NedSpace

Suite 250, SW 11th Avenue, Portland

Thanks to Mike Pumphrey for arranging the venue for the Sunday Sprint.

• MULTIPOLYGON
• MULTILINESTRING
• MULTIPOINT

• Un seul éditeur SQL de PgAdmin III doit être ouvert.

• Pour que la ou les requête(s) soient exécutées, il ne faut pas être positionné sur un nom de table dans le navigateur d'objets de PgAdmin III , ou alors que la table soit déjà chargée dans le visualiseur.  Une table sélectionnée prendra toujours le pas sur une ou des requêtes.

• Le premier champ doit être  géométrique ou une géométrie issue d'une fonction de traitement géométrique (ST_Buffer, ST_Intersection....) par requête sera utilisé pour l'affichage. Ce champ ou cette géométrie sera encapsulé par la fonction AsBinary et aura pour alias geom :
• SELECT AsBinary(wkb_geometry) as geom ....
• SELECT AsBinary(ST_Buffer(wkb_geometry, 1.0)) as geom...
• SELECT AsBinary(ST_Intersection(a.wkb_geometry,b.wkb_geoemetry)) as geom... 
• ....

•  Le second champ doit permettre de déterminer le type de géométrie, il doit donc être encapsulé par la fonction GeometryType, un alias n'est pas nécessaire :
• SELECT ..., GeometryType(wkb_geometry)...
• SELECT ..., GeometryType(ST_Buffer(wkb_geometry,1.0))...
• SELECT ..., GeometryType(ST_Intersection(a.wkb_geometry,b.wkb_geometry))...
• ....

• Chaque requête devra se terminer par un point virgule, ce qui permettra de pouvoir exécuter plusieurs requêtes a la suite.

• La première requête va charger la commune qui a pour nom 'Sainte-Croix-de-Quintillargues'
• La seconde requête va charger tous les bâtiments de cette commune.

July 22, 2014 Portland, Oregon, USA Excitement builds as FOSS4G 2014 approaches! Join us in Portland, Oregon this September 8th – 13th.  Attending FOSS4G in Portland is a once in a lifetime opportunity.  FOSS4G is an incredible conference; 2013 was in Nottingham (UK) and 2015 will be in Seoul (South Korea), but this year, FOSS4G is right in your backyard in Portland, Oregon September 8th -13th!  Workshops are filling up — register [1] now to secure your seat in pre-conference workshops and your place at the conference. Call for Maps! Represent the beauty of the Pacific Northwest in map form in the Map Gallery.  We invite contributions to the FOSS4G Map Gallery to build an exciting and vibrant exhibit of the very best in mapping. This map gallery will not only demonstrate the work of delegates but also act as a reference point for the current state of mapping.  We encourage all delegates to share one example of their work and help us create a cartographic record of the FOSS4G 2014 conference.  Read the full call for maps [2] and enter your map [3]. Workshops and general sessions program This year FOSS4G features more than 40 workshops [4], providing excellent training opportunities on relevant, leading technologies — and that’s all before the conference even begins.  With eight tracks [5] of sessions, plus invited talks and a great selection of Keynote Speakers, it will be a FOSS4G packed week to remember. Keynote biographies See exciting keyntoes by Mike Bostock of D3.js fame and the New York Times, Sarah Novotny of NGINX and a program chair for O’Reilly Media’s OSCON, and Al Shaw whose work at ProPublica has been honored with several awards. About FOSS4G The annual FOSS4G conference is the largest global gathering focused on open source geospatial software. FOSS4G brings together developers, users, decision-makers and observers from a broad spectrum of organizations and fields of operation. Through six days of workshops, presentations, discussions, and cooperation, FOSS4G participants create effective and relevant geospatial products, standards, and protocols. FOSS4G has been held all over the world and draws attendees from over 40 countries. Nottingham, England hosted the conference in 2013. In 2014, Portland, Oregon, USA will host FOSS4G’s tenth year. Important Conference Dates See the full calendar [6] for more details. Sep 8th-9th: Workshops Sep 10th-12th: Main Conference Sep 13th: Code Sprint Links [1] Registration: http://foss4g2014.eventbrite.com/ [2] Call for Maps: https://2014.foss4g.org/foss4g-call-for-maps/ [3] Map Submissions: https://2014.foss4g.org/gallery-submissions/ [4] Workshops: https://2014.foss4g.org/schedule/workshops/ [5] Sessions: http://2014.foss4g.org/schedule/sessions/ [6] Calendar:https://2014.foss4g.org/about/calendar/ Sponsors Gold Level Sponsors Silver Level Sponsors          Bronze Level Sponsors                Supporters                                    Media Partners These leading geospatial media organizations have partnered with FOSS4G to keep their readers informed.                                                                                           For more information or to keep informed from the FOSS4G Organizing Committee, follow @foss4g on Twitter, subscribe to our announcements list, or contact: foss4g2014-info@osgeo.org

The post Are you excited yet? Program details, Call for Maps, and more appeared first on FOSS4G 2014.

The GeoServer team is overjoyed to announce the release of GeoServer 2.6-beta.

I hope you are enjoying the new website – the download page for 2.6-beta provides links to the expected zip, war, dmg and exe bundles. For this release we are experimenting with providing source downloads directly from the GitHub 2.6-beta tag.

As a development release, 2.6-beta is considered experimental and is provided for testing purposes. This release is not recommended for production (even if you are excited by the new features).

This release is made in conjunction with GeoTools 12-beta. Thanks to Kevin for making a beta release of GeoWebCache 1.6.0-beta with relatively little notice.

What to expect … and what we expect from you

A complete change log is available from the issue tracker. We will ask you to wait for 2.6.0 before we let Andrea write a pretty blog with pictures illustrating what features have been added. Instead 2.6-beta is my chance to ask you to download GeoServer 2.6-beta for testing.

Testing is a key part of the open source social contract. The GeoServer team have identified a few areas where we would like to ask for help. This is your best chance to identify issues early while we still have time to do something about it. For those making use of commercial support ask your vendor about their plans for 2.6-beta testing. We would like to ensure the functionality you depend on is ready to go for a Q2 release.

When testing Geoserver 2.6-beta please let us know on the user list (or #GeoServer) how it works for you. We will be sure to thank you in the final release announcement and product presentations.

Java 7 Testing

With Oracle retiring Java 6 security updates the time has come to raise the minimum bar to Java 7.

We know a lot of downstream projects (such as OSGeo Live) have been waiting for GeoServer to support Java 7. Thanks to CSIRO, Boundless, GeoSolutions for providing Java 7 build environments allowing us to make this transition in a responsible fashion.

Testing:

• This is a major testing priority on all platforms.
• Windows 7: The start.bat used by the run manually install has trouble running as an administrator. We recommend installing as a service of this release (GEOS-5687)
• Mac: You will need to install Oracle Java 7 (as OpenJDK 7 is not yet available for OSX). We have not yet figured out how to run GeoServer.App with Java 7 (GEOS-6588) and are open to suggestions.

References:

• Documentation: Java Considerations and Installation
• Change Control: GSIP 112 Update master to Java 7

WFS Cascade

This is a really exciting change, swapping out our gt-wfs client code for a new gt-wfs-ng implementation with a new GML parser / encoder.  After comparing quality of the two implementations we decided to go all in with this transition .. and thus would really like your help testing.

We would like to hear back on cascading the following configurations:

• GeoServer
• deegree
• MapServer
• tinyows - there is a critical fix about axis order in tinyows trunc. It corrects (finally!) the output … but perhaps not yet the filters?
• ArcGIS
• Other – any other WFS you are working with!

Testing:

• Pay special attention to the flags used for axis order. There are different flags to account for each way a WFS implementation can get confused. You will find some implementations expect the wrong axis order on request, but are capable of producing the correct axis order output.
• We especially ask our friends in Europe to test WFS services published for INSPIRE compliance

This was an epic amount of work by Niels and we have a couple of new features waiting in the wings based on the success of this transition.

Curves support for GML and WMS

A large amount of work has been put into extending the Geometry implementation used by GeoServer.

We have experimented with several approaches over the years (including ISO 19107 and a code sprint with the deegree project) and it is great to finally have a solution. As a long time user of the JTS Topology Suite we have been limited to a Point, Line and Polygon model of Geometry. Andrea has very carefully extended these base classes in to allow for both GML output and rendering. The trick is using a tolerance to convert the the arcs and circles into line work for geometry processing.

Testing for the 2.6-beta release is limited to those with Oracle Spatial. If you are interested in funding/volunteering support for PostGIS please contact the geoserver-devel email list.

Testing:

• Look for “Linearization tolerance” when configuring your layer.

Advanced projection handling for raster

We would like to hear feedback on how maps that cross the date line (or are in a polar projection) have improved for you.

Testing:

• No special settings needed

Reference:

• Advanced Raster Projection in GeoServer (GeoSolutions)

Coverage Views

We struggled a bit with how to name this great new feature, however if you work with raster data this is your chance to recombine bands from different sources into a multi-band coverage.

Testing:

• Use “Configure new Coverage view” when creating a new layer

References:

• Coverage Views (GeoServer User Manual)
• Raster Views in GeoServer via the CoverageView concept (GeoSolutions)

Startup Testing

Yes this is an ominous item to ask you to test.

GeoServer 2.6 simplifies where configuration files are stored on disk. Previous versions were willing to spread configuration files between the webapps folder, the data directory and any additional directories on request. For GeoServer 2.6 configuration files are limited to the data directory as a step towards improving clustering support and growing our JDBC Config story.

Testing:

• No special settings needed
• Special request to check files that are edited by hand on disk (such security settings and free marker templates)

References:

• Change Control: GSIP 106 ResourceStore API

Pluggable Styles

For everyone happy with the CSS Style Extension we would like to ask you to test a change to the style edit page (allowing you to create a CSS or SLD style from the start).

Testing:

• Install CSS Extension and look for a new option when creating a style

Reference:

• Change Control: GSIP 117 Pluggable Styles

Wind barbs and WKT Graphics

I am really happy to see this popular extension folded into the main GeoServer application.

Testing:

• Check GeoTools WKT Marks for examples you can use in your SLD file

References:

• Supporting Wind Barbs In GeoServer and GeoTools (GeoSolutions)

New Formats and Functionality

We have new implementations of a couple of modules:

• Printing – new implementation from our friends at MapFish
• Scripting – includes a UI for editing scripts from the Web Administration Application

A final shout out to ask for help testing new formats:

• NetCDF
• Rib
• OGR

Language Support

We are happy to announce the first release having support for Turkish. Many thanks to Engin Gem and the whole translation team for the initial contribution. All modules, core, extensions, and community modules have been translated within 8 month. Great success!

French, Korean, Polish, Romanian were corrected and updated to the latest developments. Thanks to all GeoServer Transifex translators and Frank for managing!

Spot a translation mistake? Help translate here: GeoServer Latest localizations

About GeoServer 2.6

Articles and resources for GeoServer 2.6 series:

• Raster Views in GeoServer via the CoverageView concept (GeoSolutions)
• Advanced Raster Projection in GeoServer (GeoSolutions)
• Supporting Wind Barbs In GeoServer and GeoTools (GeoSolutions)
• GeoServer now supports Vector Footprints for ImageMosaic (GeoSolutions)

• Web mapping with OGC services and GeoServer: an introduction (Workshop) 14th of July between 9 A.M. and 12 A.M.
• GeoServer on steroids (Presentation) 15th of July at 2 P.M.
• Processing Data In GeoServer With Rendering Transformations, WPS Processes And SQL Views (Presentation) 15th of July at 5 P.M.
• GeoServer, An Introduction For Beginners (Presentation) 16th of July at 3:30 P.M.

Update

Hola a todos de nuevo,

Hacia ya un tiempo que no escribía por aquí…cosas de ir bastante liado con nuevos desarrollos que estamos abordando en gvSIG…pero el otro día me comentaron que necesitarían una herramienta en gvSIG que les permitiera localizar problemas en las geometrías de una tabla antes de cargar dicha tabla en una BBDD de postgreSQL.

Me dijeron…

“Estaría bien disponer de una herramienta que procese las geometrías de una capa y me saque un listado con los problemas y me permita pinchar e ir a la geometría conflictiva y mejor aun a donde este el conflicto”

Efectivamente, gvSIG no tiene nada que se le parezca, pero enseguida pensé que igual con un poco de scripting podía sacar algo parecido a lo que me pedían.

El script no es simple, para que vamos a engañarnos, toca muchos palos, pero no es muy grande y puede servir de inicio para abordar cosas mas complejas.

El principio es simple… nos recorremos las features de la capa, cogemos la geometría, e invocamos al método “getValidationStatus” de esta. Este método realiza una serie de validaciones sobre la geometría y nos devuelve que ha pasado con esas validaciones… si todo fue bien o mal, y en caso de ir mal nos da información sobre que problema se encontró y si puede donde lo encontró. Con esta información, vamos a ir construyendo un pequeño informe en HTML.

Por cada incidencia que encontremos generaremos una entrada con:

• El número de línea en el que se produjo la incidencia
• Un volcado de los datos de la feature asociada a esa línea
• Una descripción textual del problema
• Un enlace al punto en donde se produjo la incidencia. En el hiperenlace, en lugar de poner una URL meteremos el punto en WKT asociado a la incidencia.

wktgeom = vs.getProblemLocation().convertToWKT()
output.write('<a href="%s">%5.5d</a> %s<br>%s' % (wktgeom,i, feature.toString(),vs.getMessage()))

application = ApplicationLocator.getManager()
application.showTextDialog(
  WindowManager.MODE.TOOL,
  "Problems in layer "+layer.getName(),
  informe.getvalue()
)

class MyHyperlinkListener(HyperlinkListener):
  def __init__(self,vista):
    self.vista = vista
    
  def hyperlinkUpdate(self, h):
    if str(h.getEventType()) == "ACTIVATED":
      wktgeom = h.getDescription()
      print wktgeom
      manager = GeometryLocator.getGeometryManager()
      point = manager.createFrom(wktgeom)
      centerViewinPoint(self.vista,point)

manager = GeometryLocator.getGeometryManager()
point = manager.createFrom(wktgeom)

centerViewinPoint(self.vista,point)

try:
  # Añadimos la barra de progreso a la barra de estado de gvSIG
  taskStatus.add()
  # Le indicamos cuantas iteraciones vamos a realizar
  taskStatus.setRangeOfValues(0,layer.features().getCount())
  for feature in layer.features():
    # En cada iteración informamos a la barra de progreso de por donde vamos
    taskStatus.setCurValue(i)
    ...
    i+=1
finally:  
  # Al terminar
  # Le indicamos a la barra de progreso que ya hemos terminado
  taskStatus.terminate()
  # Y la eliminamos de la barra de estado de gvSIG.
  taskStatus.remove()

from gvsig import *
from org.gvsig.tools.swing.api.windowmanager import WindowManager
import StringIO
from commonsdialog import *
from javax.swing.event import HyperlinkListener
from org.gvsig.fmap.geom import GeometryLocator
from org.gvsig.fmap.geom import Geometry

def centerViewinPoint(view,center):
    env = view.getMap().getViewPort().getEnvelope();
    movX = center.getX()-env.getCenter(0);
    movY = center.getY()-env.getCenter(1);
    minx = env.getMinimum(0) + movX;
    miny = env.getMinimum(1) + movY;
    maxX = env.getMaximum(0) + movX;
    maxY = env.getMaximum(1) + movY;
    env = GeometryLocator.getGeometryManager().createEnvelope(
          minx, miny,
          maxX, maxY,
          Geometry.SUBTYPES.GEOM2D);
    view.getMap().getViewPort().setEnvelope(env);
    view.getMap().invalidate()


class MyHyperlinkListener(HyperlinkListener):
  def __init__(self,vista):
    self.vista = vista
    
  def hyperlinkUpdate(self, h):
    if str(h.getEventType()) == "ACTIVATED":
      # Sopo procesamos los eventos "ACTIVATED" que son los clicks sobre los enlaces
      # Recogemos la geometría que metimos en el enlace en WKT
      wktgeom = h.getDescription()
      print wktgeom
      # Y reconstruimos el punto a partir de ese WKT
      manager = GeometryLocator.getGeometryManager()
      point = manager.createFrom(wktgeom)
      # Y una vez lo tenemos centramos la vista en ese punto.
      centerViewinPoint(self.vista,point)


def main(*args):
  layer = currentLayer()
  if layer == None:
    msgbox("Debera seleccionar la capa que desea validar")
    return
  informe = StringIO.StringIO()  
  informe.write("<ul>\n")
  i=0
  hay_problemas = False
  try:
    # Añadimos la barra de progreso a la barra de estado de gvSIG
    taskStatus.add()
    # Le indicamos cuantas iteraciones vamos a realizar
    for feature in layer.features():
      # En cada iteración informamos a la barra de progreso de por donde vamos
      taskStatus.setCurValue(i)
      vs = feature.geometry().getValidationStatus();
      if not vs.isValid() :
        hay_problemas = True
        if vs.getProblemLocation()!=None:
          wktgeom = vs.getProblemLocation().convertToWKT()
        else:
          try:
            # Atrapamos los errores no vaya a ser que la geometría este tan dañada que
            # nos falle el calculo de su centroide.
            wktgeom = feature.geometry().centroid().convertToWKT()
          except:
            wktgeom = None
        informe.write("<li>")
        if wktgeom == None:
          informe.write('%5.5d%s<br>%s' % (i, feature.toString(),vs.getMessage()))
        else:
          informe.write('<a href="%s">%5.5d</a> %s<br>%s' % (wktgeom,i, feature.toString(),vs.getMessage()))
        informe.write("</li>")
      i+=1
  finally:  
    # Al terminar
    # Le indicamos a la barra de progreso que ya hemos terminado
    taskStatus.terminate()
    # Y la eliminamos de la barra de estado de gvSIG.
    taskStatus.remove()
    
  informe.write("</ul>\n")
  if hay_problemas :
    application = ApplicationLocator.getManager()
    application.showTextDialog(
      WindowManager.MODE.TOOL, # TOOL o WINDOW según nos interese.
      "Problems in layer "+layer.getName(),
      informe.getvalue(),
      MyHyperlinkListener(currentView())
    )
  else:
    msgbox("Layer "+layer.getName()+" is valid.")

The GeoServer team is happy to announce the release of GeoServer 2.5.2. Download bundles are provided (zip, war, dmg and exe)  along with documentation and extensions.

GeoServer 2.5.2 is the next the stable release of GeoServer and is recommended for production deployment. Thanks to everyone taking part, submitting fixes and new functionality:

• Some fixes in the new GetFeatureInfo engine, for unfilled polygons and dashed lines
• Solved a configuration issue that might have linked two styles toghether (edit one, the other changed as well)
• DBMS connection leak in some WFS GetFeature with bounds enabled
• Have WPS work properly as a workspace specific service, and report the current process activity during asynchronous requests (for processes that do report what they are doing in plain english, besides offering a progress percentage)
• Add a way to resctrict output formats supported by WMS GetMap and GetFeatureInfo
• More docs on how to setup JNDI connection pools in GeoServer
• Thanks to Andrea (GeoSolutions) for publishing this release
• Check the release notes for more details
• This release is made in conjunction with GeoTools 11.2

About GeoServer 2.5

Articles and resources for GeoServer 2.5 series:

• GeoServer now supports Vector Footprints for ImageMosaic
• Harvesting Metadata using CSW
• Caveats in GeoServer JNDI configuration
• Supporting Wind Barbs In GeoServer and GeoTools
• Deterministic rendering order in SLDs
• Secure GeoServer connections to Postgres for Heroku
• Labelling a MultiPoint geometry with WPS
• GeoServer 2.5-beta announcement reviews key features of this release:
  • WCS 2.0 and WCS 2.0 Earth Observation have been added (thanks to DLR and Eumesat for funding this)
  • The addition of a batch importer to making setting up GeoServer easier (thanks to MapStory).
  • High performance PNG encoder based on PNGJ library (Andrea Aime). Improved JPEG performance using libjpegturbo available as an optional extension (Simone Giannecchini and Daniele Romagnoli)
  • Use of ST_Simplify to improve PostGIS rendering performance (a collaboration with Andrea and Jonathan Moules).
  • New implementation of GetFeatureInfo that takes into account symbol shapes, offsets, and dynamic line widths into account (thanks to Eskilstuna municipality for funding this).
• Using GeoServer at IGN to create new digital maps is an impressive look at advanced styling deployed by the french mapping agency
• Labelling a MultiPoint geometry with WPS (Boundless) is a good example of integrating WPS and Styling
• Achieving extreme GeoServer Scalability with new Marlin vector rasterizer (GeoSolutions) shows an exciting JRE extension that can be used for improved performance. If you are using GeoServer with a large number of CPU cores you owe yourself an hour to try this out.
• DXF output format promoted to official extension for GeoServer (GeoSolutions)
• Active Directory based security in GeoServer through LDAP (GeoSolutions)

Boundless is growing but our focus remains helping customers build the best web mapping applications. We’ve recruited a stronger leadership team and are enhancing our current products while also developing new products and services to help customers in new ways.

We recently added Ann Johnson as our new CEO to strengthen our team and leadership. Ann’s experience with enterprise software, particularly her deep knowledge of security, greatly expand our expertise in critical areas of Spatial IT.

At the same time, we have been steadily adding capabilities to OpenGeo Suite to enable easier, more scalable web services deployments. To help our customers successfully build enterprise mapping applications, we’re advancing open source software like OpenLayers 3 and providing new SDK templates that leverage this new technology. We continue to “lower the cost of free software” by making secure, fault tolerant, and scalable deployments of our open source stack simpler, faster, and easier.

Additionally, some of our key initiatives include:

• Releasing new online training courses and on-site classes that enable us to train many more users on how to deploy and administer GeoServer and PostGIS.

• Expanding our professional services offerings to make developing, implementing, and perfecting open source solutions quicker and easier.

• Expanding our partner program to create new capabilities (such as new options for Big Data) and grow internationally.

• Increasing ways to help QGIS users easily work with, style, and publish data to the web.

With Ann joining Boundless, I’m focusing my efforts on developing these and other capabilities to grow our business, with a particular emphasis on developing new partnerships to create a new geospatial ecosystem based on open source software. We believe the future is bright for open source–based solutions to address a variety of challenges, from publishing data to asset management to customer services. I look forward to working with our customers and partners to reshape this industry!

The post Boundless Growth appeared first on Boundless.

GeoSolutions è lieta di annunciare l’accordo di Partnership raggiunto con l’azienda Esalab S.r.l. grazie al quale Esalab S.r.l. rappresenterà GeoSolutions  nelle regioni di Marche, Abruzzo e Basilicata.

L’accordo di Partnership tra GeoSolutions e Esalab costituisce l’inizio di un percorso che ha l’obiettivo di creare una rete di imprese coinvolte nello sviluppo e nella promozione dei principali software geospaziali Open Source da sempre promossi e sviluppati da GeoSolutions. La costruzione di una rete di imprese dislocate sul territorio nazionale e internazionale in grado di supportare gli utenti e di promuovere professionalmente i software geospaziali Open Source GeoServer, GeoNetwork e MapStore mira a raggiungere un ulteriore miglioramento dei servizi offerti.

I partner di GeoSolutions saranno formati direttamente dai technical lead di GeoSolutions e saranno, come nel caso dell’azienda Esalab, partner strategici già coinvolti a vario titolo nello sviluppo e nell’utilizzo dei software geospaziali Open Source promossi e curati da GeoSolutions in modo da garantire ai clienti dei partner la possibilità di interagire direttamente con coloro che sviluppano i software supportati per garantire una efficacia di servizio senza pari.

L’integrazione tra i tecnici di GeoSolutions e quelli delle aziende partner dislocate sul territorio è pensata nell’ottica di fornire al cliente finale un supporto ancora più presente e professionale attraverso un parco consulenti articolato ed eterogeneo capace di affrontare qualsiasi problematica in modo efficiente ed efficace.

Chi è GeoSolutions

GeoSolutions è un’azienda altamente specializzata  nella gestione, processamento e disseminazione  dei dati geospaziali sia raster che vettoriali tramite l’utilizzo di software Open Source secondo le specifiche dettate dall’Open  GeoSpatial Consortium  (OGC) e dell’ ISO Technical Committee 211 che a loro volta forniscono  la base delle regole di INSPIRE ed RNDT.

GeoSolutions è composta da professionisti di livello internazionale con esperienza pluriennale nella progettazione, realizzazione e supporto di infrastrutture Enterprise per la gestione di dati geospaziali. I membri dello staff di GeoSolutions sono a vario titolo leader di alcuni tra i principali prodotti  Open Source  per  il  mondo  geospaziale come GeoServer, GeoNetwork MapStore e GeoTools e forniscono per essi supporto professionale avanzato.

GeoSolutions annovera tra  i  suoi principali  clienti  enti  pubblici nazionali ed internazionali così come aziende private di tutto il mondo. United  Nations Food  and  Agriculture Organization (FAO),  United Nations World Food Program (WFP), NATO STO CMRE, EUMETSAT, German Space Agency (DLR), Austrian MetOffice (ZAMG), CSI Piemonte, Norwegian Public Roads Administration (NPRA), Magistrat Wien e tanti altri si avvalgono della collaborazione di GeoSolutions così come il Comune di Firenze e la Provincia di Firenze,  il Comune di Prato e la Provincia di Prato, il Comune di Bolzano ed il Comune di Genova.

Chi è Esalab

Esalab s.r.l. è una società fondata nel 1998 che opera nell'ambito della progettazione, dello sviluppo e dell'implementazione di Sistemi Informativi, rivolgendo la propria attività agli Enti Pubblici ed alle grandi società di Ingegneria.

Esalab è specializzata nella definizione di servizi specifici di web application e di soluzioni integrate Web-GIS per la gestione del territorio, per il monitoraggio ambientale, per la protezione civile e per il turismo in ambito Open Source, secondo le specifiche dell’Open GeoSpatial Consortium (OGC) e di INSPIRE.

Esalab dispone di un team di lavoro dedicato alla ricerca e alla realizzazione di progetti innovativi nel campo delle tecnologie GIS e WEBGIS.

Esalab annovera tra i suoi principali clienti enti pubblici nazionali e società di ingegneria: Regione Marche, Provincia di Barletta Andria Trani, Comune di Urbino, SAIPEM SpA, Proger SpA e numerosi comuni nel territorio nazionale.

GeoSolutions Alliance Partnership Program

Il programma GeoSolutions Alliance Partnership si rivolge alla aziende che supportano e propongono i prodotti Open Source sviluppati da GeoSolutions e che sono alla ricerca di un partner capace di offrire il necessario supporto tecnico, commerciale e di marketing per lo sviluppo del proprio mercato. Per maggiori informazioni si rimanda alla pagina dedicata, oppure si consiglia di contattarci direttamente menzionando il GeoSolutions Alliance Partnership Program.

When mapping flows or other values which relate to a certain direction, styling these layers gets interesting. I faced the same challenge when mapping direction-dependent error values. Neighboring cell pairs were connected by two lines, one in each direction, with an associated error value. This is what I came up with:

Each line is drawn with an offset to the right. The size of the offset depends on the width of the line which in turn depends on the size of the error. You can see the data-defined style properties here:

To indicate the direction, I added a marker line with one > marker at the center. This marker line also got assigned the same offset to match the colored line bellow. I’m quite happy with how these turned out and would love to hear about your approaches to this issue.

These figures are part of a recent publication with my AIT colleagues: A. Graser, J. Asamer, M. Dragaschnig: “How to Reduce Range Anxiety? The Impact of Digital Elevation Model Quality on Energy Estimates for Electric Vehicles” (2014).

GeoSolutions and Esalab are glad to announce their Partnership.

Esalab will be the exclusive representative company of the OpenSDI Suite (GeoServer, GeoWebCache, GeoNetwork and MapStore) for the following italian regions: Marche, Abruzzo and Basilicata.

Since more than ten years Esalab develops products and projects relating to geospatial field based on GeoServer and integrated with GeoNetwork.

The Partnership program between GeoSolutions and Esalab allows the two companies to offer a more and more qualified support to the end users.

GeoSolutions Alliance Program

GeoSolutions Alliance Program is the partnership program for companies that want to extend their market reach by adding or boosting their skills on GeoSpatial Open Source Products leveraging on a collaboration with GeoSolutions Team.

The goal is to create a network of certified partners which are able to support the growth and deeper penetration of Open Source GeoSpatial Products by positively addressing the increased demand for professional support services and solutions.

Check this page for additional information.

n viewer 3D pour PostGIS

ntroduction

Avec la version 2.0 PostGIS est entré dans le monde de la 3D, il est possible de stocker des géométries 3D avec l’ajout de la coordonnée Z dans toutes les géométries existantes et de stocker des géométries volumétriques avec l’introduction de deux nouveaux type  :

TIN(Triangulated Irregular Network, une collection de TRIANGLE)
POLYHEDRALSURFACE (une collection de POLYGON)

Cela fait déjà un an que la création d’un viewer pour visualiser les géométries 3D de PostGIS me trottait dans la tête suite à un échange avec Claus Nagel et Felix Kunde de virtualcitySYSTEMS à propos de l’outil d’import du format CityGML que j’avais réalisé CityGML vers PostGIS 2.0 , ils m’avaient conseillé alors de me diriger vers le développement d’un viewer 3D. Lorsque récemment j’ai repris contact avec eux pour leur parler de mon développement en cours, ils ont accueilli la nouvelle avec enthousiasme et ont bénéficié de versions beta, ce qui m’a grandement aidé pour mes choix dans la finalisation de mon application.

Aujourd’hui la 3D est de plus en plus présente dans le monde SIG avec le format CityGML et dans le monde de l’architecture avec le format IFC, importer ces formats dans une base de données PosgtgreSQL/PostGIS est une démarche naturelle car cela apporte toute la puissance de traitement des bases de données spatiale pour la gestion de ces données.

Pour le format CityGML la société virtualcitySYSTEMS met à disposition un schéma de base de données Open Source et gratuit pour le stockage et la gestion de ‘3D City Models’. Ce schéma de base de données est le reflet du modèle de données CityGML. Les données peuvent être importées via un outil d’import/export . le lien pour accéder à leur site : http://virtualcitysystems.de/en/solutions.html#3dcitydb

A ce stade du développement je n’affiche que des géométries de type POLYGON, MULTIPOLYGON, TIN et POLYHEDRALSURFACE. Ce qui permet d’afficher toutes type de géométries volumétriques répondant à cette contrainte. Je vais travailler rapidement sur les autres type de géométrie POINT, LINESTRING… , ce qui fera l’objet d’une nouvelle version de l’application dans les prochaines semaines.

J’ai développé cet outil en C# 2013 avec :

La librairie GDAL/OGR		GDAL - Geospatial Data Abstraction Library
ActiViz .Net un wrapper pour VTK		ActiViz .Net
		VTK
PostgreSQL 9.2		PostgreSQL Windows
PostGIS 2.2.0 dev		Postgis http://winnie.postgis.net/download/windows/pg92/buildbot/postgis-pg92-binaries-2.2.0devw32.zip http://winnie.postgis.net/download/windows/pg92/buildbot/postgis-pg92-binaries-2.2.0devw64.zip

Pour l’intégration de données 3D j’ai testé l’outil 3DCityDB-Importer-Exporter http://http://www.3dcitydb.org/3dcitydb/downloads/ qui permet d’importer des fichiers au format CityGML dans une base de données PostgreSQL avec PostGIS (a partir de la version 2.0).

Voici une extraction du document 3DCityDB-v2_0_6-postgis-Tutorial.pdf concernant la partie PostGIS (en anglais ) :

nstallation

Cliquez sur le lien pg3DViewer_setup.exe pour télécharger le programme d’installation, puis lancer l’exécution. Cliquer sur le  bouton Suivant à chaque étape, puis sur le bouton Terminer.

tilisation

Avant de commencer à utiliser pg3Dviewer vous devez avoir une base de données PostgreSQL avec la cartouche spatiale PostGIS version 2.0 ou supérieure. Cette base de données doit contenir des données 3D, l’idéal serait que vous ayez créé une base 3DCityDB et importé un ou plusieurs fichiers CityGML. Voici un lien ou vous pourrez télécharger des données CityGML Rotterdam 3D, demandez à notre ami Google de traduire la page cela peut aider, cela permet de découvrir un lien sur le site permettant de télécharger un fichier pdf contenant une carte avec tous les nom des quartiers téléchargeables http://www.rotterdam.nl/GW/Images/Gemeentewerken%20Home/Landmeten/overzicht%20buurten.pdf , il ne vous reste plus qu’a choisir les quartiers dans la liste sous le lien.

Vous pouvez quand même faire les premiers tests sans avoir téléchargé de données.

Double cliquez sur l’icone créé par le programme d’installation sur le bureau pour lancer l’application.

Connecter vous à votre base de données 3D

	Commencez par cliquer sur cet icône pour vous connecter a une base de données PostgreSQL/PostGIS version 2.0 ou supérieur contenant des données 3D ou prête à en recevoir.
	Choisissez localhost pour serveur si votre base de données est en local sur votre machine ou bien saisissez l’adresse IP de votre serveur le port est par défaut 5432, changez le si nécessaire saisissez l’utilisateur saisissez le mot de passe choisissez une base de donnée dans la combobox cliquez sur le bout OK pour valider votre saisie.

Visualiser une géométrie de type POLYHEDRALSURFACE

Dans le panneau Query copiez la requête suivante : SELECT st_force_collection(     st_geomFromText     (        'POLYHEDRALSURFACE(         ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)),         ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)),         ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)),         ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)),         ((1 0 0, 1 1 0, 1 1 1, 1 0 1, 1 0 0)),         ((1 1 0, 0 1 0, 0 1 1, 1 1 1, 1 1 0))         )'     ) )
Cliquez sur l’icone ‘Execute query’
Vous obtenez ce résultat. Interactions de la souris avec la fenêtre de rendu: - Bouton gauche : Rotation - Roulette          : Zoom - Bouton droit    : Zoom dynamique - Bouton gauche + touche majuscule : Pan Testez les différentes associations entre les touches Majuscule, Ctrl et alt et  les boutons de la souris. Interactions touches claviers avec la fenêtre de rendu : - Touche w : passe en mode affichage fil de fer. - Touche s  : passe en mode affichage surfacique.
La fenêtre de rendu après rotation.

Visualiser une géométrie de type TIN

Dans le panneau Query copiez la requête suivante : WITH res AS ( SELECT st_polygon(     st_boundary(         (st_dump(             st_geomFromText             (            'TIN(             ((0 0 0, 1 0 0, 0 1 0, 0 0 0)),             ((0 0 0, 1 0 0, 0 0 1, 0 0 0)),             ((0 0 0, 0 0 1, 0 1 0, 0 0 0)),             ((0 0 1, 1 0 0, 0 1 0, 0 0 1))             )'             )         )).geom     )     ,0     ) as geom ) SELECT st_forceCollection(st_collect(geom)) FROM res

Cliquez sur l’icone ‘Execute query’ Vous obtenez ce résultat après rotation.

Fonction passant d’une géométrie de type TIN à une géométrie de type GEOMETRYCOLLECTION Z

Vous allez créer la fonction dans votre base de données 3D :

• Copier le contenu du cadre ci-dessus et collez dans la fenêtre de requêtes de PgAdmin III
• lancez l’exécution, la fonction est créée.

la requête pour l’affichage de géométrie de type TIN devient alors:

select st_astext(ST_TinToGeomCollection(
st_geomFromText
            (
            'TIN(
            ((0 0 0, 1 0 0, 0 1 0, 0 0 0)),
            ((0 0 0, 1 0 0, 0 0 1, 0 0 0)),
            ((0 0 0, 0 0 1, 0 1 0, 0 0 0)),
            ((0 0 1, 1 0 0, 0 1 0, 0 0 1))
            )'
            ) ,0))
le second paramètre de la fonction ST_TinToGeomCollection étant le SRID de la géométrie, 4326 par exemple si vous êtes dans un système de coordonnées WGS84. Si vous ne le connaissez pas saisissez la valeur 0.

Affichage de données dans une base 3DCityDB contenant des données au format CityGML

Dans le panneau Query copiez la requête suivante : WITH wallsurface as ( SELECT a.id,c.root_id,st_collect(c.geometry) AS g,'255:128:0'::text AS rgb FROM building a,thematic_surface b, surface_geometry c WHERE b.building_id=a.id AND b.type='WallSurface' AND c.root_id=b.lod2_multi_surface_id GROUP BY a.id,c.root_id ), roofsurface as ( SELECT a.id,c.root_id,st_collect(c.geometry) AS g,'255:0:0'::text AS rgb FROM building a,thematic_surface b, surface_geometry c WHERE b.building_id=a.id AND b.type='RoofSurface' AND c.root_id=b.lod2_multi_surface_id GROUP BY a.id,c.root_id ) select id,root_id,g as geom,rgb from wallsurface union all select id,root_id,g as geom,rgb FROM roofsurface ORDER BY id
Cliquez sur l’icone ‘Execute query’
Dans la requête il est possible d’affecter une couleur à un type de géométrie, la syntaxe est le code R:G:B entre quotte suivi de AS rgb : ’255:128:0’ AS rgb  (wallsurface) ‘255:0:0’     AS rgb  (rootsurface)

Interface

	Sortie de l’application.
	Connexion à une base de données.
	Panneau Requête
	Remet à blanc la fenêtre de requêtes
	Ouvre un fichier requête, qui ne doit contenir qu’une seule requête.
	Exécution de la requête.
	Collapse le panneau sur la gauche.
	Panneau affichage 3D
	Change la cuouleur du fond, Blanc ou Noir.
	Zoom Full.
	Zoom Plus.
	Zoom Moins.
	Efface le contenu de la fenêtre de rendu, toutes les géométries précédemment chargées sont supprimées.
	Panneau données attributaires
	Collapse le panneau sur le bas.

onclusion.

Ce billet met à votre disposition un outil permettant de visualiser des géométries 3D stockées dans une base de données PostGIS 2.0 ou supérieure. Il me reste à implémenter l’affichage des points et des lignes.

Toutes suggestions d’amélioration seront les bienvenues, j’attends vos retours.

n viewer 3D pour PostGIS

ntroduction

Avec la version 2.0 PostGIS est entré dans le monde de la 3D, il est possible de stocker des géométries 3D avec l’ajout de la coordonnée Z dans toutes les géométries existantes et de stocker des géométries volumétriques avec l’introduction de deux nouveaux type  :

TIN(Triangulated Irregular Network, une collection de TRIANGLE)
POLYHEDRALSURFACE (une collection de POLYGON)

Cela fait déjà un an que la création d’un viewer pour visualiser les géométries 3D de PostGIS me trottait dans la tête suite à un échange avec Claus Nagel et Felix Kunde de virtualcitySYSTEMS à propos de l’outil d’import du format CityGML que j’avais réalisé CityGML vers PostGIS 2.0 , ils m’avaient conseillé alors de me diriger vers le développement d’un viewer 3D. Lorsque récemment j’ai repris contact avec eux pour leur parler de mon développement en cours, ils ont accueilli la nouvelle avec enthousiasme et ont bénéficié de versions beta, ce qui m’a grandement aidé pour mes choix dans la finalisation de mon application.

Aujourd’hui la 3D est de plus en plus présente dans le monde SIG avec le format CityGML et dans le monde de l’architecture avec le format IFC, importer ces formats dans une base de données PosgtgreSQL/PostGIS est une démarche naturelle car cela apporte toute la puissance de traitement des bases de données spatiale pour la gestion de ces données.

Affichage de données CityGML dans le viewer 3D

Continuer la lecture/Continue reading “PostGIS 3D Viewer”

Новая статья, посвящённая созданию тайлового сервера с помощью стека технологий, используемого для создания тайлов на сайте OpenStreetMap.

Прочитать | Обсудить

• ShowLegend
• ShowNorthArrow
• ShowCoordinates
• ShowScaleBar
• ShowLegalDisclaimer (does nothing if there is no legal disclaimer attached or AllowDisclaimerToggle = false)

  <onlineMapSource>
    <name>mapguide-rest Sheboygan</name>
    <url><![CDATA[http://localhost/mapguide/rest/library/Samples/Sheboygan/MapsTiled/SheboyganNoWatermark.MapDefinition/xyz/Base Layer Group/{$z}/{$x}/{$y}/tile.png]]></url>
    <tileFormat>png</tileFormat>
    <servers></servers>
  </onlineMapSource>

• Specify the path of the MBTiles database you want to create
• Trace a box around the area you want to fetch the tiles for
• Tick the Download Levels (aka. Zoom levels) you want to fetch tiles for. The map preview shows the current zoom level, so generally you want to tick that level and every level above that.
• Tick Compact? to optimize storage of redundant tiles

• Fix: Bad sample code and data in light of the Sheboygan dataset update.
• Fix: v2.6 QUERYMAPFEATURES cannot append/update viewer selections via shift-click in AJAX and Fusion viewers.
• Fix: v2.6 QUERYMAPFEATURES cannot handle dates before Jan 1, 1970.
• Fix: GEOMETRY parameter in QUERYMAPFEATURES operation should be optional. QUERYMAPFEATURES should be able to accept a query geometry (via GEOMETRY) or an XML selection string (via FEATUREFILTER) when updating viewer selections.
• Remove setselection AJAX viewer helper script which is made redundant with the above fix.
• Fusion: Add int16 identity property support for search widget.
• Fusion: Allow blank titles in print widget.
• Fusion: Preserve inner stack trace (if possible) when reporting back un-handled AJAX errors.

Do you use PostGIS and/or PostgreSQL?

As you are planning your FOSS4G travel, here’s another excellent event to have on your radar.

Saturday, September 6th, is PostgreSQL Day, co-hosted by the Portland Postgres Users Group (PDXPUG)  and Portland State University. Attendance is free, but RSVP is required (RSVP here). See below for more details on the event.

Looking forward to seeing you in September!

Date: Saturday, September 6, 2014

Time: 9:30am through 5:30pm

Place: Portland State University, Room EB 102, 1930 SW 4th Avenue, Portland, Oregon 97201. The venue is reachable by street car, bus or light rail, see Tri-Met for schedule and fare information.

Registration: Space is limited, please RSVP!

Food: Light snacks & beverages provided. Breakfast and lunch is on your own. There’s a wonderful cart pod right across the street; bring $10-15 for lunch.

Presentations: Organizers are looking for presenters for the PDXPUG Day. Talks should be about 45 minutes in length, and about any of the following topics:

• PostgreSQL administration and performance
• Case studies of interesting uses of PostgreSQL and PostGIS
• Interesting applications built on PostGIS or PostgreSQL
• Database and/or geographic application development
• Database-related DevOps
• SQL and stored procedure programming
• New Postgres/PostGIS features and hacking Postgres/PostGIS

Organizers will also be taking lightning talks of 5 minutes each, on similar topics. Email your talk proposal to Mark Wong at markwkm -at- postgresql.org.

The post RSVP for PostgreSQL Day, Saturday September 6th appeared first on FOSS4G 2014.