[OSM-dev] Effort in the US wasted until TIGER import
NRover at websitemakers.com
Wed Mar 28 14:42:29 BST 2007
Thats fine we can put the data in as short ways, rather than one long
way, the point I was trying to make was this. If imported from text
files it would look like this
county a county b
o---------o X o---------o
If we did it from the database we could make it look like this
county a county b
Key: o=node o----o=way
The last time a TIGER import was attempted each segment was a way and
there was a break between them. This could be very confusing for routing
software to navigate down the road, if it's not linked at the nodes.
When importing on a county by county base there would be a break right
at the county line. If all the data is in the database and everything
regarding the road is queried at once we could avoid this problem.
Dirk-Lüder Kreie wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Nathan Rover schrieb:
>> Sorry, I've been a little busy this week, I'm going to start setting up
>> the server on Thursday. I've got about 3/4 of the states downloaded (4.8
>> GB zipped). I was going to load Debian on the server, are there any
>> objections? After looking at the TIGER data, I've started thinking that
>> it might work better to import the data as is into a mySQL database.
>> Some of the files are just records of keys from other records in other
>> files, ect, ect, ect. This could be why the original scrips only
>> imported info from one of the files. There is much more information
>> available but you need to be able to join data from different files.
>> Going county by county will also be a problem if the data is imported
>> from the files. Case in point look at I-70, how many counties does I-70
>> go through as it crosses the country? If you go county by county each
>> segment will be a way, rather then the whole road.
> You wouldn't want to have the entire I-70 as one long way. Long ways get
> impossible to edit if they can't be downloaded by bounding box. make
> segments of 10-20 km of it. Or fit it into ~0.15 degree bounding boxes.
> Dirk-Lüder "Deelkar" Kreie
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
More information about the dev