rcoup
commented
12 years ago Good for the record, but no point looking at it until the feature ID stuff is done by LINZ and we have a strategy/plan to merge updates.
Closed edcorkery closed 12 years ago
rcoup
commented
12 years ago Good for the record, but no point looking at it until the feature ID stuff is done by LINZ and we have a strategy/plan to merge updates.
HamishB
commented
12 years ago just wondering, what's the cleanest workflow method for LINZ data service WFS --> PostGIS? aka is shp2pgsql lossy in that situation? is there a better middleman than .shp? :-/ csv + local parsing tool?
thanks, Hamish
HamishB
commented
12 years ago I wrote:
what's the cleanest workflow method for LINZ data service WFS --> PostGIS?
nevermind, found this: http://www.linz.govt.nz/sites/default/files/about-linz/lds/Importing-LDS-CSV-data-into-your%20database.pdf
Hamish B
rcoup
commented
12 years ago We can use the (almost released) changeset service to get just features that have been modified between releases. Should make life simpler
Rob :)
On Thursday, 6 September 2012 at 2:58 PM, HamishB wrote:
I wrote:
what's the cleanest workflow method for LINZ data service WFS --> PostGIS?
nevermind, found this: http://www.linz.govt.nz/sites/default/files/about-linz/lds/Importing-LDS-CSV-data-into-your%20database.pdf
Hamish B— Reply to this email directly or view it on GitHub (https://github.com/opennewzealand/linz2osm/issues/82#issuecomment-8320985).
This is a highly desirable feature for LINZ (one of The Funders) and other Government agencies.
Ideally linz2osm would suck in data from the WFS vector layers of the LINZ Data Service (LDS, http://data.linz.govt.nz), and any other future WFS service, e.g. if the NZ Transport Agency launched WFS services in the future for their state highway data.
Each LINZ layer already configured in linz2osm should have a related WFS source in LDS.
Future value: In a couple of months, topo data from LDS will have unique identifiers and WFS changesets between data versions available.