Zip and Installer files The .zip files are just the binaries you can copy intoyour PostgreSQL installation and then enable in each database as usual. The exe are standard windows setup for 64-bit PostgreSQL.
If you are more adventurous, and risk-seeking you can partake in our experimental windowsbinaries of PostGIS built automatically by Winnie whenever there is a change in any of the PostGIS Stable or development branches.These are especially useful for testing out new features or if you are badly in need of a bug fix that has not been released yet.
If you don't want to risk messing up an existingwindows install or aren't allowed to write to the registry, we'd suggest using the companion PostgreSQL EDB binaries-only binaries which don't require installation.Setup is detailed in Starting PostgreSQL in windows without install.
Inspection of failures, are crashes of the backend. I'm having similar issue with building the 2.0.1 64-bit for 9.2 on my windows 7 64-bit. The annoying thing is if I run the statements manually that cause the crash, they don't crash.
If you are on windows and want to give some of this all a test drive, you can download one of our PostGIS 2.0.0 Windows experimental builds. We still only have 32-bit builds. We have buildsfor PostgreSQL 8.4, PostgreSQL 9.0, and PostgreSQL 9.1 beta 2. The problems we faced in PostgreSQL 9.1 beta 1 were resolved in beta 2 so that most regress tests past except some minor ones involving stupid things like difference in line number marking of errors. Complement your PostgreSQL 9.1 beta 2 meal with a yummy large helping of PostGIS 2.0.0 goodness.
Sandro Santilli (strk) has been diligently working on Topology support to make our PostGIS topology more inline with SQL-MM standards. Andrea Peri has also been helping out a great deal with testing and providing some patches. I still hope to create a loader for TIGER data (which in itself is a topological model) very close in structure to PostGIS topology. Both systems are composed of edges, faces, and nodes as the basic building blocks. This will serve as both a good learning tool for topology, a good way to stress test the system with real world data, as well as providing useful data that people would want to work with anyway. Not sure if I will get to that before release, so might come as a separate add-on.Tiger Geocoder Finally got the loader fully functional on Linux/Unix I think and I have been surprised how many people have already started using it and posting bug reports and patches. We are still working on speed improvements that we are doing via our consulting work and will contribute back in the code base. It still intentionally works fine with PostGIS 1.5 since we are improving on it for clients currently using PostGIS 1.5. However some of the new changes we have made require 8.4 or higher.Much improved 3D Support - as mentioned before we have new 3D indexes, operators, functions and types (TINS, POLYHEDRAL SURFACES etc). Though I don't show it , this is the part that I am most excited about. I'm still fleshing out the ST_ASX3D - making enhancements and hope to release a tutorial showing how to create a simple web-based 3D query tool with x3dom and PostGIS.Shape file dumper /loaders get some love We now have transformation support in the shape file loader, multi-file import for the gui shapefile loader and some other goodies.PostGIS 64-bit builds -- when are they coming?First I must say aside from a few people who have whined, I don't get the sense that people care too much either way with running PostGIS under 64-bit PostgreSQL windows install. Our interest is mostly out of curiosity if it will work better than it does under 32-bit Windows. Despite most people's snide remarks about running PostgreSQL on windows, it works fairly well for many of our needs and the PostGIS speed is for the most part on par with the Linux speed. There are still many suites that only work on windows and where having both a Linux box and windows box to maintain is not worth the hassle for the marginal difference in speed.
The Nuvoton NANO120LC2BN is a Core - ARM Cortex-M0 core running up to 42 MHz - Supports Low Power Sleep mode - NVIC for 32 interrupt inputs, with 4-levels priority - Serial Wire Debug Flash EPROM Memory - 64K/32K/123K bytes application program memory (APROM) - 4 KB in system programming (ISP) loader program memory (LDROM) - Programmable data flash start address and memory size - ISP/IAP to update on-chip Flash EPROM SRAM Memory - 16K/8K bytes embedded SRAM DMA - 8 channels CRC - 3 common polynomials CRC-CCITT (CRC-8, CRC-16, CRC-32) Clock Control - Built-in 12 MHz OSC - Low power 10 kHz OSC for watchdog and low power system operation - PLL, up to 120 MHz, for high performance system operation and USB application (48 MHz) - External 4~24 MHz crystal input - External 32.768 kHz crystal input GPIO - 3 I/O modes (Push-Pull output, Open-Drain output, Input only with high impendence) Timer - 4 sets of 32-bit timers Watchdog Timer Window Watchdog Timer(WWDT) RTC - RTC counter (second, minute, hour), calendar counter (day, month, year) - 80 bytes spare registers PWM/Capture - 2 PWM modules, each has 2 16-bit PWM generators UART - Up to 2 16-byte FIFO UART controllers - IrDA (SIR), LIN, RS-485 9 bit mode SPI - Up to 3 sets of SPI controller - Master up to 32 MHz, Slave up to 16 MHz I2C - Up to 2 sets of I2C device - Master/Slave up to 1 Mbit/s I2S - Interface with external audio CODEC - Capable of handling 8, 16, 24, 32 bit word sizes ADC - 12-bit SAR ADC up to 2Msps conversion rate DAC - 12-bit monotonic output with 400K conversion rate Touch Key(TK) - up to 16 touch-keys scanning SmartCard (SC) - up to 3 ISO-7816-3 ports EBI (External bus interface) support - 64 KB in 8-bit mode or 128 KB in 16-bit mode - 8bit/16bit data width - byte write in 16-bit Data Width mode One built-in temperature sensor 96-bit unique ID 128-bit unique customer ID Brown-out - Built-in 2.5V/2.0V/1.7V BOD. 2b1af7f3a8