On Thu, Jan 1, 2009 at 6:14 PM, Steve Singer wrote:
> The geobase2osm.py script lets you pass a bounds file (with the -b option).
> This will only include roads that pass through the bounds specified in the
> file. So you can take the full provincial GML files but only generate .osm
> files for
On Thu, Jan 1, 2009 at 5:28 PM, Jason Reid
wrote:
> In terms of actually adding the data into OSM, the only real solution is to
> use the API and the bulk_upload tool (or a tool with equivalent
> functionality).
But that bulk_upload tool has no provisions for checking for and
possibly matching e
On Thu, 1 Jan 2009, James Ewen wrote:
> Can you slice the GML file up into chunks? We could manually start the
> import process by manually defining areas where we want to start
> importing data. Areas chosen by users with little or no existing data.
The geobase2osm.py script lets you pass a bou
James Ewen wrote:
> On Thu, Jan 1, 2009 at 4:17 PM, Jason Reid
> wrote:
>
>
>> The script will generate a single OSM file per GML file, so 1 per
>> province currently.
>>
>
> Any plans on how to merge the OSM and GeoBase files into one database?
>
>
>> The mapping between the Geobase ta
On Thu, Jan 1, 2009 at 4:17 PM, Jason Reid
wrote:
> The script will generate a single OSM file per GML file, so 1 per
> province currently.
Any plans on how to merge the OSM and GeoBase files into one database?
> The mapping between the Geobase tags and OSM tags is a work in progress
> still, i
Thanks to some patches from Steve Singer, I've committed a new version
of the NRN import script to the SVN repository. This version uses the
python OGR bindings to better process the source data, and Steve also
worked out a system to merge junction nodes together (earlier versions
of the script
6 matches
Mail list logo
