OSGeo Planet

Gis-Lab: Вышел OSGeo-Live 11.0

OSGeo Planet - Wed, 2017-08-09 17:48

Вышла очередная версия “геодистрибутива” Linux – OSGeo-Live 11.0.

Основные изменения связаны с удалением программ, которые мало развиваются или не поддерживаются, и сосредоточением на крупных проектах и документации.

Более подробная информация здесь.

Categories: OSGeo Planet

GeoSolutions: New release of MapStore with vector editing support

OSGeo Planet - Wed, 2017-08-09 15:36

Vector Editing

Dear Reader,

we are pleased to announce a new release of MapStore, our flagship Open Source webgis product, which we have called 2017.04.00. The full list of changes for this release can be found here, but the latest most interesting additions are the following.

  • Support for vector layer editing (via WFS-T)
  • Direct access to the data grid from the TOC
  • New data grid with a better look & feel
  • Advanced search moved from the TOC into a separate panel, accessible directly from the feature grid
  • Legacy maps (from MapStore version 1) are identified. The author that access to a legacy map will be guided to update.
  • Localization in Spanish
Support for vector layer editing

This release gives you the opportunity do edit your vector data. If you integrated the authentication system with GeoServer, you will be able to login as administrator and edit your vector data's attributes and Geometries.

[gallery type="slideshow" ids="3631,3634,3652,3643,3642"] Improved access to the vector data with a new data grid. 

Now you can browse data for vector layer in a more intuitive way. You can open the data grid directly from the TOC, without using the query panel. The new data grid has a toolbar on top to access to the main functionalities (search, editing, download...), where available. Advanced search is still accessible from the feature grid.

[gallery type="slideshow" ids="3650,3647,3646,3645"]

If you want to play with the improved feature grid we have loaded some data from Atlantis (yeah, we know where it is, just don't spread the word...) in a MapStore simplified application that you can find here. Don't worry if you mess the data, every night the original data will be restored!

[gallery type="slideshow" ids="3676,3679"] Guided update for legacy maps

The user will be notified when a map that was created with MapStore 1 needs to be updated, if he has the right permissions to do that. Clicking on Update button the update will be performed automatically.

[gallery type="slideshow" ids="3661,3660"] Future Work

The work for the next releases will be focused on TOC & Catalog style review plus code hardening. Take a look on the Proposal or the interactive mockup (both still in progress) for an early preview.

If you are interested in learning about how we can help you achieving your goals with open source products like GeoServerMapstore, GeoNode and GeoNetwork through our Enterprise Support Services and GeoServer Deployment Warranty offerings, feel free to contact us!

The GeoSolutions team,
Categories: OSGeo Planet

Jackie Ng: React-ing to the need for a modern MapGuide viewer (Part 18): Restoring the Quick Plot capture box

OSGeo Planet - Wed, 2017-08-09 14:47
If you've been playing with mapguide-react-layout, you'll no doubt have noticed a glaring omission in the ported Quick Plot component.

The interactive map capture box.


Porting across the capture box sounded mostly simple:

  • Manage the temporary OL vector layer containing the capture box.
  • Attach an OL translate interaction so the capture box feature can be easily moved around by dragging the box around.
  • Auto-update box geometry based on change in paper size / orientation / scale
There was just one technical hurdle: Rotating the box.
For the longest time, I was wracking my brain figuring out how to replace the rotation "grip handle" using the new OpenLayers APIs and I couldn't figure it out. The APIs were there to rotate feature geometry. I heard about ol-rotate-feature and gave it a try, but I couldn't grasp how that interaction actually rotates features.
So I went back to the mental drawing board. OpenLayers has APIs to rotate features, so what we really just need was an intuitive UI input to enter the box rotation. If I couldn't figure out how to replicate the rotation "grip handle", then the next best thing was ... a numerical slider.
And with that, the missing piece was found and I was finally able to port over the final piece of functionality of the original Fusion QuickPlot widget.

In the above GIF, you might have noticed a message flash by.

This is merely a simple countermeasure against the fact that with current OpenLayers, you can rotate the map as well. So rather than deal with number crunching 2 sets of rotations, it is easier to just reset the rotation on the map and prevent the ability to rotate the map while the map capture box is active.
And with that, our Quick Plot component has reached feature parity with the original Fusion widget.
This (newly feature parity) Quick Plot will be available in the next release of mapguide-react-layout, whenever I decide that will be.
Categories: OSGeo Planet

OSGeo News: OSGeo-Live 11.0 Released

OSGeo Planet - Wed, 2017-08-09 07:02
Categories: OSGeo Planet

Paul Ramsey: My FOSS4G 2017 List

OSGeo Planet - Tue, 2017-08-08 21:00

Because I was asked.

We can't wait to see all the other goodies on your list! #foss4g https://t.co/RkNhQR3wkW

— FOSS4G 2017 (@foss4g) August 8, 2017

Here’s my 2017 FOSS4G list:

One week and I’ll be in Boston, looking forward to it!

Categories: OSGeo Planet

Oslandia: OSM data quality assessment: producing map to illustrate data quality

OSGeo Planet - Tue, 2017-08-08 12:20

At Oslandia, we like working with Open Source tool projects and handling Open (geospatial) Data. In this article series, we will play with the OpenStreetMap (OSM) map and subsequent data. Here comes the eighth article of this series, dedicated to the OSM data quality evaluation, through production of new maps.

1 Description of OSM element  1.1 Element metadata extraction

As mentionned in a previous article dedicated to metadata extraction, we have to focus on element metadata itself if we want to produce valuable information about quality. The first questions to answer here are straightforward: what is an OSM element? and how to extract its associated metadata?. This part is relatively similar to the job already done with users.

We know from previous analysis that an element is created during a changeset by a given contributor, may be modified several times by whoever, and may be deleted as well. This kind of object may be either a “node”, a “way” or a “relation”. We also know that there may be a set of different tags associated with the element. Of course the list of every operations associated to each element is recorded in the OSM data history. Let’s consider data around Bordeaux, as in previous blog posts:

import pandas as pd elements = pd.read_table('../src/data/output-extracts/bordeaux-metropole/bordeaux-metropole-elements.csv', parse_dates=['ts'], index_col=0, sep=",") elements.head().T elem id version visible ts uid chgset 0 node 21457126 2 False 2008-01-17 24281 653744 1 node 21457126 3 False 2008-01-17 24281 653744 2 node 21457126 4 False 2008-01-17 24281 653744 3 node 21457126 5 False 2008-01-17 24281 653744 4 node 21457126 6 False 2008-01-17 24281 653744

This short description helps us to identify some basic features, which are built in the following snippets. First we recover the temporal features:

elem_md = (elements.groupby(['elem', 'id'])['ts'] .agg(["min", "max"]) .reset_index()) elem_md.columns = ['elem', 'id', 'first_at', 'last_at'] elem_md['lifespan'] = (elem_md.last_at - elem_md.first_at)/pd.Timedelta('1D') extraction_date = elements.ts.max() elem_md['n_days_since_creation'] = ((extraction_date - elem_md.first_at) / pd.Timedelta('1d')) elem_md['n_days_of_activity'] = (elements .groupby(['elem', 'id'])['ts'] .nunique() .reset_index())['ts'] elem_md = elem_md.sort_values(by=['first_at']) 213418 elem node id 922827508 first_at 2010-09-23 00:00:00 last_at 2010-09-23 00:00:00 lifespan 0 n_days_since_creation 2341 n_days_of_activity 1

Then the remainder of the variables, e.g. how many versions, contributors, changesets per elements:

elem_md['version'] = (elements.groupby(['elem','id'])['version'] .max() .reset_index())['version'] elem_md['n_chgset'] = (elements.groupby(['elem', 'id'])['chgset'] .nunique() .reset_index())['chgset'] elem_md['n_user'] = (elements.groupby(['elem', 'id'])['uid'] .nunique() .reset_index())['uid'] osmelem_last_user = (elements .groupby(['elem','id'])['uid'] .last() .reset_index()) osmelem_last_user = osmelem_last_user.rename(columns={'uid':'last_uid'}) elements = pd.merge(elements, osmelem_last_user, on=['elem', 'id']) elem_md = pd.merge(elem_md, elements[['elem', 'id', 'version', 'visible', 'last_uid']], on=['elem', 'id', 'version']) elem_md = elem_md.set_index(['elem', 'id']) elem_md.sample().T elem node id 1340445266 first_at 2011-06-26 00:00:00 last_at 2011-06-27 00:00:00 lifespan 1 n_days_since_creation 2065 n_days_of_activity 2 version 2 n_chgset 2 n_user 1 visible False last_uid 354363

As an illustration we have above an old two-versionned node, no more visible on the OSM website.

1.2 Characterize OSM elements with user classification

This set of features is only descriptive, we have to add more information to be able to characterize OSM data quality. That is the moment to exploit the user classification produced in the last blog post!

As a recall, we hypothesized that clustering the users permits to evaluate their trustworthiness as OSM contributors. They are either beginners, or intermediate users, or even OSM experts, according to previous classification.

Each OSM entity may have received one or more contributions by users of each group. Let’s say the entity quality is good if its last contributor is experienced. That leads us to classify the OSM entities themselves in return!

How to include this information into element metadata?

We first need to recover the results of our clustering process.

user_groups = pd.read_hdf("../src/data/output-extracts/bordeaux-metropole/bordeaux-metropole-user-kmeans.h5", "/individuals") user_groups.head() PC1 PC2 PC3 PC4 PC5 PC6 Xclust uid 1626 -0.035154 1.607427 0.399929 -0.808851 -0.152308 -0.753506 2 1399 -0.295486 -0.743364 0.149797 -1.252119 0.128276 -0.292328 0 2488 0.003268 1.073443 0.738236 -0.534716 -0.489454 -0.333533 2 5657 -0.889706 0.986024 0.442302 -1.046582 -0.118883 -0.408223 4 3980 -0.115455 -0.373598 0.906908 0.252670 0.207824 -0.575960 5

As a remark, there were several important results to save after the clustering process; we decided to serialize them into a single binary file. Pandas knows how to manage such file, that would be a pity not to take advantage of it!

We recover the individuals groups in the eponym binary file tab (column Xclust), and only have to join it to element metadata as follows:

elem_md = elem_md.join(user_groups.Xclust, on='last_uid') elem_md = elem_md.rename(columns={'Xclust':'last_uid_group'}) elem_md.reset_index().to_csv("../src/data/output-extracts/bordeaux-metropole/bordeaux-metropole-element-metadata.csv") elem_md.sample().T elem node id 1530907753 first_at 2011-12-04 00:00:00 last_at 2011-12-04 00:00:00 lifespan 0 n_days_since_creation 1904 n_days_of_activity 1 version 1 n_chgset 1 n_user 1 visible True last_uid 37548 last_uid_group 2

From now, we can use the last contributor cluster as an additional information to generate maps, so as to study data quality…

Wait… There miss another information, isn’t it? Well yes, maybe the most important one, when dealing with geospatial data: the location itself!

1.3 Recover the geometry information

Even if Pyosmium library is able to retrieve OSM element geometries, we realized some tests with an other OSM data parser here: osm2pgsql.

We can recover geometries from standard OSM data with this tool, by assuming the existence of an osm database, owned by user:

osm2pgsql -E 27572 -d osm -U user -p bordeaux_metropole --hstore ../src/data/raw/bordeaux-metropole.osm.pbf

We specify a France-focused SRID (27572), and a prefix for naming output databases point, line, polygon and roads.

We can work with the line subset, that contains the physical roads, among other structures (it roughly corresponds to the OSM ways), and build an enriched version of element metadata, with geometries.

First we can create the table bordeaux_metropole_geomelements, that will contain our metadata…

DROP TABLE IF EXISTS bordeaux_metropole_elements; DROP TABLE IF EXISTS bordeaux_metropole_geomelements; CREATE TABLE bordeaux_metropole_elements( id int, elem varchar, osm_id bigint, first_at varchar, last_at varchar, lifespan float, n_days_since_creation float, n_days_of_activity float, version int, n_chgsets int, n_users int, visible boolean, last_uid int, last_user_group int );

…then, populate it with the data accurate .csv file…

COPY bordeaux_metropole_elements FROM '/home/rde/data/osm-history/output-extracts/bordeaux-metropole/bordeaux-metropole-element-metadata.csv' WITH(FORMAT CSV, HEADER, QUOTE '"');

…and finally, merge the metadata with the data gathered with osm2pgsql, that contains geometries.

SELECT l.osm_id, h.lifespan, h.n_days_since_creation, h.version, h.visible, h.n_users, h.n_chgsets, h.last_user_group, l.way AS geom INTO bordeaux_metropole_geomelements FROM bordeaux_metropole_elements as h INNER JOIN bordeaux_metropole_line as l ON h.osm_id = l.osm_id AND h.version = l.osm_version WHERE l.highway IS NOT NULL AND h.elem = 'way' ORDER BY l.osm_id;

Wow, this is wonderful, we have everything we need in order to produce new maps, so let’s do it!

2 Keep it visual, man!

From the last developments and some hypothesis about element quality, we are able to produce some customized maps. If each OSM entities (e.g. roads) can be characterized, then we can draw quality maps by highlighting the most trustworthy entities, as well as those with which we have to stay cautious.

In this post we will continue to focus on roads within the Bordeaux area. The different maps will be produced with the help of Qgis.

2.1 First step: simple metadata plotting

As a first insight on OSM elements, we can plot each OSM ways regarding simple features like the number of users who have contributed, the number of version or the element anteriority.

Figure 1: Number of active contributors per OSM way in Bordeaux

 

Figure 2: Number of versions per OSM way in Bordeaux

With the first two maps, we see that the ring around Bordeaux is the most intensively modified part of the road network: more unique contributors are implied in the way completion, and more versions are designed for each element. Some major roads within the city center present the same characteristics.

Figure 3: Anteriority of each OSM way in Bordeaux, in years

If we consider the anteriority of OSM roads, we have a different but interesting insight of the area. The oldest roads are mainly located within the city center, even if there are some exceptions. It is also interesting to notice that some spatial patterns arise with temporality: entire neighborhoods are mapped within the same anteriority.

2.2 More complex: OSM data merging with alternative geospatial representations

To go deeper into the mapping analysis, we can use the INSEE carroyed data, that divides France into 200-meter squared tiles. As a corollary OSM element statistics may be aggregated into each tile, to produce additional maps. Unfortunately an information loss will occur, as such tiles are only defined where people lives. However it can provides an interesting alternative illustration.

To exploit such new data set, we have to merge the previous table with the accurate INSEE table. Creating indexes on them is of great interest before running such a merging operation:

CREATE INDEX insee_geom_gist ON open_data.insee_200_carreau USING GIST(wkb_geometry); CREATE INDEX osm_geom_gist ON bordeaux_metropole_geomelements USING GIST(geom); DROP TABLE IF EXISTS bordeaux_metropole_carroyed_ways; CREATE TABLE bordeaux_metropole_carroyed_ways AS ( SELECT insee.ogc_fid, count(*) AS nb_ways, avg(bm.version) AS avg_version, avg(bm.lifespan) AS avg_lifespan, avg(bm.n_days_since_creation) AS avg_anteriority, avg(bm.n_users) AS avg_n_users, avg(bm.n_chgsets) AS avg_n_chgsets, insee.wkb_geometry AS geom FROM open_data.insee_200_carreau AS insee JOIN bordeaux_metropole_geomelements AS bm ON ST_Intersects(insee.wkb_geometry, bm.geom) GROUP BY insee.ogc_fid );

As a consequence, we get only 5468 individuals (tiles), a quantity that must be compared to the 29427 roads previously handled… This operation will also simplify the map analysis!

We can propose another version of previous maps by using Qgis, let’s consider the average number of contributors per OSM roads, for each tile:

Figure 4: Number of contributors per OSM roads, aggregated by INSEE tile

2.3 The cherry on the cake: representation of OSM elements with respect to quality

Last but not least, the information about last user cluster can shed some light on OSM data quality: by plotting each roads according to the last user who has contributed, we might identify questionable OSM elements!

We simply have to design similar map than in previous section, with user classification information:

Figure 5: OSM roads around Bordeaux, according to the last user cluster (1: C1, relation experts; 2: C0, versatile expert contributors; 3: C4, recent one-shot way contributors; 4: C3, old one-shot way contributors; 5: C5, locally-unexperienced way specialists)

According to the clustering done in the previous article (be careful, the legend is not the same here…), we can make some additional hypothesis:

  • Light-blue roads are OK, they correspond to the most trustful cluster of contributors (91.4% of roads in this example)
  • There is no group-0 road (group 0 corresponds to cluster C2 in the previous article)… And that’s comforting! It seems that “untrustworthy” users do not contribute to roads or -more probably- that their contributions are quickly amended.
  • Other contributions are made by intermediate users: a finer analysis should be undertaken to decide if the corresponding elements are valid. For now, we can consider everything is OK, even if local patterns seem strong. Areas of interest should be verified (they are not necessarily of low quality!)

For sure, it gives a fairly new picture of OSM data quality!

3 Conclusion

In this last article, we have designed new maps on a small area, starting from element metadata. You have seen the conclusion of our analysis: characterizing the OSM data quality starting from the user contribution history.

Of course some works still have to be done, however we detailed a whole methodology to tackle the problem. We hope you will be able to reproduce it, and to design your own maps!

Feel free to contact us if you are interested in this topic!

Categories: OSGeo Planet

gvSIG Team: 13th International gvSIG Conference: Registration is now open

OSGeo Planet - Tue, 2017-08-08 12:05

The registration period for the 13th International gvSIG Conference is now open. The conference has been moved earlier this year, and it will be held from October 18th to 20th in Valencia (Spain).

Registrations are free of cost (limited capacity) and must be done through the application form on the Conference web page.

The conference program and all the information about registration for the workshops that are planned, and about the conference rooms will be available at the event website soon.

We also remind you that we have extended the deadline for submitting communication proposals. The extended deadline is September 7th. You can find all the information about communication sending in the event website.

We expect your participation!


Filed under: community, english, events, training Tagged: 13th gvSIG Conference
Categories: OSGeo Planet

gvSIG Team: 13as Jornadas Internacionales gvSIG: Inscripción abierta

OSGeo Planet - Tue, 2017-08-08 12:01

Ya está abierto el periodo de inscripción de las 13as Jornadas Internacionales gvSIG, que tendrán lugar este año en octubre, concretamente del 18 al 20, en Valencia (España).

La inscripción es totalmente gratuita (con aforo limitado) y se ha de realizar a través del formulario existente en la página web de las Jornadas.

Más adelante se publicará el programa con todas las ponencias y los talleres previstos, con toda la información sobre cómo inscribirse en ellos.

Por otro lado, os recordamos que se ha ampliado el plazo de envío de resúmenes, siendo la nueva fecha límite el 7 de septiembre. Las normas para el envío de comunicaciones podéis encontrarlas en la propia web.

¡Esperamos vuestra participación!


Filed under: community, events, spanish, training Tagged: 13as Jornadas gvSIG
Categories: OSGeo Planet

Fernando Quadro: Curso de GeoServer em Setembro

OSGeo Planet - Tue, 2017-08-08 11:59

Caros leitores,

Quero convidá-los a participarem do Curso Online de GeoServer que estarei ministrando pela GEOCURSOS. O objetivo do curso é que você aprenda a disponibilizar, compartilhar e editar dados geográficos na internet com o GeoServer.

No curso serão abordados tópicos como: configuração de dados, criação de estilo com SLD, padrões OGC, interface administrativa (web), visualização cartográfica com OpenLayers, REST API, Segurança, entre outros.

O curso ocorrerá entre os dias 19 e 28 de setembro(terças, quartas e quintas) das 20:00 as 22:00 (horário de Brasília).

Aqueles que poderem divulgar para seus contatos, agradeço. Quem quiser saber mais informações sobre o curso, pode obtê-las no site do curso (http://www.geocursos.com.br/geoserver), twitter (http://twitter.com/geo_cursos) e pelo facebook (http://www.facebook.com/geocursosbr).

Categories: OSGeo Planet

gvSIG Team: Towards gvSIG 2.4: Access to gvSIG Desktop help

OSGeo Planet - Tue, 2017-08-08 10:11

At the next version of your favourite GIS we have added a pair of options at the “Help” menu that will be used a lot. Sometimes the simplest things are the most useful ones. They allow to access to all the contents of the gvSIG Desktop user manual as well as to search the appropriate documentation for a concrete query.

Simple, easy and extremely useful.


Filed under: english, gvSIG Desktop, testing Tagged: documentation, manual
Categories: OSGeo Planet

GeoSolutions: Meet GeoSolutions at INSPIRE Conference 2017

OSGeo Planet - Tue, 2017-08-08 09:21

inspire-conf-2017-latest

Dear All, we are proud to announce that GeoSolutions is exhibiting at the INSPIRE Conference 2017 which will be held in Strabourg and Kehl from 4th to 8th of September 2017.

GeoSolutions will be present with its own booth therefore we will be happy to talk to you about our open source products, like GeoServerMapstore, GeoNode and GeoNetwork, as well as about our Enterprise Support Services and GeoServer Deployment Warranty offerings.

We are going to hold a workshop on GeoServer for INSPIRE as well as a few presentations as follows:

  • Publishing INSPIRE services with GeoServer and HALE (Workshop), Monday, September 4, 2017 - 9:00, Room f
  • Building Interoperable SDI with GeoServer, Mapstore and GeoNetwork: experiences from the trenches, Friday, September 8, 2017, 14:45, Room Amsterdam

There will also be a short corporate presentation for which the exact date and time is yet to publish; we will update this post once we have precise information.

Our director Simone Giannecchini will also participate in the workshop:

  • GeoICT SMEs as key-players in the INSPIRE driven innovation: the role of the smeSpire network, Tuesday, September 5, 2017 - 9:00, Romm A

If you are interested in learning about how we can help you achieving your goals with our Open Source products and professional services, make sure to visit us at our booth

The GeoSolutions team,
Categories: OSGeo Planet

gvSIG Team: gvSIG 2.3.1 in macOS Sierra

OSGeo Planet - Tue, 2017-08-08 08:49

As you know, there are portable gvSIG Desktop versions for para macOS, Windows and Linux. Portable version was released for macOS Mavericks, and a series of problems have been detected, that prevented using it in macOS Sierra.

With the objective to spread it more, we have echoed about the information published at the blog about gvSIG and Mac to solve these problems and use your favourite GIS in macOS Sierra:

There’s a problem with another library, now libc ++.1.dylib but after removing it, it seems to work.

Our current configuration, like any other Mac running Sierra (we think it), has libc ++. 1.dylib in /usr/lib, so it’s not necessary to have the same library inside gvSIG.

We have prepared a “double-click” application that will work if gvSIG-desktop-2.3.1-2501-final-darwin_macos_10.11-x86_64 is in “Applications” folder.

So, step by step:

  1. Download gvSIG 2.3.1 for mac
  2. Drag it to applications folder
  3. Open a console (the application is in Applications > Utilities folder)
  4. Write ‘mv /Applications/gvSIG-desktop-2.3.1-2501-final-darwin_macos_10.11-x86_64.app/gvSIG/extensiones/org.gvsig.gdal.app.mainplugin/gdal/libc++.1.dylib /Applications/gvSIG-desktop-2.3.1-2501-final-darwin_macos_10.11-x86_64.app/gvSIG/extensiones/org.gvsig.gdal.app.mainplugin/gdal/libc ++.1.dylib.old’, without quotation marks.
  5. Download the “double-click” aplication
  6. Double-click
  7. Enjoy it

These instructions only work if you don’t change the name of the application and you have it in applications folder.

We say goodbye thanking Agustín Díez for the work done so that gvSIG users can enjoy it in macOS Sierra.


Filed under: community, english, gvSIG Desktop, technical collaborations Tagged: Mac, Mac OS X, macOS, Sierra
Categories: OSGeo Planet

gvSIG Team: gvSIG 2.3.1 en macOS Sierra

OSGeo Planet - Tue, 2017-08-08 06:45

Como sabéis gvSIG Desktop dispone de versiones portables para macOS, Windows y Linux. La portable se publicó para macOS Mavericks y se han detectado una serie de problemas que impedían el uso en macOS Sierra.

Con el objetivo de darle mayor difusión, nos hacemos eco de la información publicada en el blog sobre gvSIG y Mac para solucionar estos problemas y poder utilizar vuestro SIG favorito en macOS Sierra:

Hay un problema con otra biblioteca, esta vez libc ++.1.dylib pero después de deshacerse de ella, las cosas parecen estar funcionando.

Mi configuración actual, como la de cualquier otro Mac ejecutando Sierra creo, tiene libc ++. 1.dylib en / usr / lib, por lo que no hay necesidad de tener la misma librería dentro de gvSIG.

He preparado una aplicación de doble clic que funcionará si gvSIG-desktop-2.3.1-2501-final-darwin_macos_10.11-x86_64 se encuentra en la carpeta Aplicaciones.

Así que paso a paso:

  1. Descargar gvsig 2.3.1 para mac
  2. Arrástralo a la carpeta de aplicaciones
  3. Abre un terminal (la aplicación está en Utilidades)
  4. Teclea ‘mv /Applications/gvSIG-desktop-2.3.1-2501-final-darwin_macos_10.11-x86_64.app/gvSIG/extensiones/org.gvsig.gdal.app.mainplugin/gdal/libc++.1.dylib /Applications/gvSIG-desktop-2.3.1-2501-final-darwin_macos_10.11-x86_64.app/gvSIG/extensiones/org.gvsig.gdal.app.mainplugin/gdal/libc ++.1.dylib.old’, sin comillas.
  5. Descarga la aplicación de doble clic
  6. Haga doble clic
  7. Disfruta

Todo esto funciona solo si no cambias el nombre de la aplicación y la pones en la carpeta de aplicaciones

Nos despedimos agradeciendo a Agustín Díez el trabajo realizado para que los usuarios de gvSIG pueden disfrutar también de él en macOS Sierra.


Filed under: gvSIG Desktop, spanish Tagged: Mac, Mac OS X, macOS, OS X, portable, Sierra
Categories: OSGeo Planet

Gis-Lab: Базовая оценка транспортной доступности средствами GRASS GIS и QGIS

OSGeo Planet - Sun, 2017-08-06 06:03

Картографирование транспортной доступности на основе данных о дорожной сети – одна из классических задач ГИС. Наиболее распространенным способом моделирования транспортной доступности является построение изохрон – линий равных затрат времени на преодоление пространства относительно заданных точек. В представленной статье обсуждается алгоритм построения изохрон по данным OpenStreetMap с использованием открытых ГИС GRASS GIS и QGIS.

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

grass-qgis-transport-blog

Categories: OSGeo Planet

gvSIG Team: Camino a gvSIG 2.4: Acceso a la ayuda de gvSIG Desktop

OSGeo Planet - Sat, 2017-08-05 14:51

En la próxima versión de vuestro SIG favorito hemos añadido un par de opciones en el menú “Ayuda” que seguro que van a ser muy utilizadas. A veces las cosas más sencillas pueden ser las más útiles. Permiten por un lado acceder a todos los contenidos del manual de usuario de gvSIG Desktop y por otro buscar la documentación adecuada a una determinada consulta.

Simple, sencillo y extremadamente útil.


Filed under: gvSIG Desktop, spanish Tagged: ayuda, gvSIG-2.4
Categories: OSGeo Planet

PostGIS Development: PostGIS 2.4.0alpha Released

OSGeo Planet - Sat, 2017-08-05 00:00

The PostGIS development team is pleased to announce the release of PostGIS 2.4.0alpha. This is the first version to support PostgreSQL 10. Best served with PostgreSQL 10beta2. See the full list of changes in the news file.

Continue Reading by clicking title hyperlink ..
Categories: OSGeo Planet

Jo Cook: moving to gitlab and hugo

OSGeo Planet - Fri, 2017-08-04 10:55
I recently decided to move this blog from octopress, hosted on a commercial site, to hugo, hosted on gitlab pages. Why? I don’t care that Octopress hasn’t been updated for a while but I do care that I didn’t understand what it was doing- I’m not a Ruby/Jekyll/Whatever person. I never took the time to understand how it worked under the hood, my bad. I wasn’t using 99% of the facilities offered with the commercial host.
Categories: OSGeo Planet

Jody Garnett: FOSS4G Europe 2017

OSGeo Planet - Fri, 2017-08-04 00:18
Enjoyed attending FOSS4G Europe, great chance to catch up with the OSGeo board for a productive face to face meeting and appreciate the vibrant community in Europe first-hand.

Thanks to the organizers for a great event. I really appreciated the chance to promote open source and share the work being done for the new OSGeo website:

There were many thoughtful talks, Ivan providing wisdom on Love, to an exhubrent Jeff McKenna speaking on the foss4g family.

I had three highlights to share:

  • Catching up with Marc Vloemans and seeing the community enjoying the new branding that everyone has worked so hard on.
  • The code sprint where the enthusiasm was brought into action: with Nicolas Roelandt stepping in to help on content collection forms when I was getting overwhelmed, along with Astrid, Luca, Venka taking on review of the printed materials.
  • Having a chance to work through design decisions with Andrea and outline the relationship between JAI-EXT project and the Raster Processing Engine. 

Thanks to Boundless for giving me an opportunity attend and speak at this community event.


https://flic.kr/s/aHskZWXreV


Categories: OSGeo Planet

Fernando Quadro: Webinar gratuito sobre qualidade e análise de utilização de serviços geoespaciais padrão OGC

OSGeo Planet - Thu, 2017-08-03 13:39

Este webinar vai abordar assuntos como análise da utilização de serviços geoespaciais padrão OGC (WMS, WFS, WMTS), como economizar tempo e dinheiro em seus processos que usam dados espaciais, automatizar de tarefas de rotina, comprovando o retorno do investimento em sua infraestrutura de dados espacias e ao mesmo tempo fornecer serviços altamente confiáveis.

Você verá com é importante conhecer o número de solicitações que os serviços podem lidar em um ambiente em constante crescimento e evolução e desta forma, garantir que a capacidade do serviço seja suficiente para atender às necessidades futuras.

Nossos clientes sabem o desempenho e quem está usando seus serviços espaciais, e você? Venha descobrir como nesse webinar que ocorrerá no dia 17/08 as 11:00h (horário de Brasília).

Link para se registrar no webinar: http://bit.ly/2vsYRIA

Categories: OSGeo Planet
Syndicate content