Alle Beiträge von Flo

ArcGIS Pro: CRS-Transformationen mit österreichbezug

Nachdem ArcGIS Pro von ESRI erwachsen wird und sukzessive vermehrt im GIS-Alltag zum Einsatz kommt, anbei ergänzend zur Serie zur Anwendung bestmöglicher Transformationsparameter zwischen dem österreichischen Bundesmeldenetz und WGS84/ETRS89 die Implementierung dieser in ArcGIS Pro (Stand Version 1.3.1).

Transformation EOSG1618 versus NTv2 AT_GIS_GRID - kleiner Unterschied
Transformation EPSG1618 (Position Vector) versus NTv2 AT_GIS_GRID – ein kleiner Unterschied


No Facebook messages/chats with mobile browser ? A detour … :-)

This week Facebook started to block the usage of Facebook messages/chats on mobile devices just with the browser – Facebook forces their „products“ (=customers) to use their messenger-App (with all the device-rights this app wants…).

A little detour allows to further use FB messages/chat with your mobile browser 🙂

Facebook forces users to use the messenger App


MongoDB and geodata part 2 – getting spatial

After importing geodata from the GIS to MongoDB and creating a spatial index (part 1), the exciting (spatial) adventure starts. With „normal“ (relational) databases and their spatial extensions (Oracle spatial, PostgreSQL/PostGIS, SQLite/Spatialite,…) a lot of spatial queries and geoprocessing are possible. So let’s try to find out which adresses have to be evacuated 250m around some „event“…

How to perform a spatial query like this with MongoDB ?


MongoDB and geodata part 1 – from Shapefile to MongoDB 3.2

MongoDB (3.2) is a kind of database-hipster at the moment – with improving support for spatial data. So it was time for me to discover some of it’s features concerning spatial data. As a GIS-user my first intention was to get some bigger simple (point) geodata into MongoDB. Part 1 covers this topic, part 2 will cover some spatial operations within MongoDB. I also want to do some performance checks between PostgreSQL/PostGIS and MongoDB related to geodata.

Geodata in QGIS and MongoDB