This project's database technology is changing to PostgreSQL.
Microsoft MapPoint 2010 is too primitive to be my comprehensive GIS solution. After a little searching, it was clear that PostgreSQL, thanks to PostGIS, dominates the database layer of GIS tools.
On top of this, I need good geospatial query support. MySql's geospatial features are minimal and apparently slow.
Fortunately, existing data is very simple tables, so data conversion is easy. But unfortunately, I put a lot of effort into learning .NET Framework 4's Entity Framework v2. The free Npgsql PostgreSQL ADO.NET provider doesn't support the DDEX necessary for full Entity Framework compatibility. (OK, so you can do Entity Framework stuff manually, but you can't do much in Visual Studio, so it is still incomplete.) I could pay for Devart's dotConnect for PostgreSQL for $180, which does support Entity Framework.
But given that no Entity Framework provider seems to support geospatial field types, it may not matter.
Decisions, decisions.
Comments
Post new comment