and to the list, sorry<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Martijn van Exel</b> <span dir="ltr"><<a href="mailto:m@rtijn.org">m@rtijn.org</a>></span><br>
Date: Wed, Mar 28, 2012 at 3:25 PM<br>Subject: Re: [Talk-us] PostGiS Queries<br>To: Hilton Long <<a href="mailto:seldomseen@scinternet.net">seldomseen@scinternet.net</a>><br><br><br>Interesting. By eliminating too close nodes you mean generalization? That should not be too difficult to do using ST_Simplify. Automatically detecting gaps is something that I am currently looking into (also for routing purposes). I was going to look at all endpoints of motorways, trunks , primaries and secondaries and look at the distance between them and the closest way of the same type or the corresponding _link type. Does that sound like a good approach to you?<br>
<br>I guess much of this was done around the original TIGER import (for example the 250 cities project[1]) but I wasn't around then to know how that was done and the wiki does not reveal very much about the processes either.<br>
<br>Martijn<br><br>[1] <a href="https://wiki.openstreetmap.org/wiki/TIGER_fixup/250_cities" target="_blank">https://wiki.openstreetmap.org/wiki/TIGER_fixup/250_cities</a><div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">
On Wed, Mar 28, 2012 at 1:58 PM, Hilton Long <span dir="ltr"><<a href="mailto:seldomseen@scinternet.net" target="_blank">seldomseen@scinternet.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks, Martijn.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">From a quick look at the links below, they seem to be routing engines. What I’m interested in is automating a review of road networks from Tiger and other data to fill gaps, eliminate too close nodes, and generally get the data so that mkgmap or cgpsmapper can handle it with a minimum of errors. I figured since all that Tiger data was uploaded there must have been an automated way to check and correct those errors. I’ve gotten PostGIS to do a lot of it, but not all, and I was hoping to find a library of routines that would save me working it all out for myself.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks again,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hilton<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">1082 N 4200 W<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Parowan, UT<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:mvexel@gmail.com" target="_blank">mvexel@gmail.com</a> [mailto:<a href="mailto:mvexel@gmail.com" target="_blank">mvexel@gmail.com</a>] <b>On Behalf Of </b>Martijn van Exel<br>
<b>Sent:</b> Wednesday, March 28, 2012 12:06 PM<br><b>To:</b> Hilton Long<br><b>Cc:</b> <a href="mailto:talk-us@openstreetmap.org" target="_blank">talk-us@openstreetmap.org</a><br><b>Subject:</b> Re: [Talk-us] PostGiS Queries<u></u><u></u></span></p>
</div><div><div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">That would have to be a pretty elaborate set of PostGIS operations.<br>This is the OSM list, so we deal with OSM data here mainly (even though TIGER is a primary data source for OSM in the US). There's several ways to make OSM data routable. See for example <a href="http://project-osrm.org/" target="_blank">http://project-osrm.org/</a> or <a href="https://wiki.openstreetmap.org/wiki/Gosmore" target="_blank">https://wiki.openstreetmap.org/wiki/Gosmore</a> - it depends on what you want to do with it. Same goes for 'managing attributes'.<br>
<br>Best<br>Martijn<br><br>-- <br>martijn van exel<br>geospatial omnivore<br>1109 1st ave #2<br>salt lake city, ut 84103<br><a href="tel:801-550-5815" value="+18015505815" target="_blank">801-550-5815</a><br><a href="http://oegeo.wordpress.com" target="_blank">http://oegeo.wordpress.com</a><u></u><u></u></p>
</div></div></div></div></blockquote></div><br><br clear="all"><br>-- <br>martijn van exel<br>geospatial omnivore<br>1109 1st ave #2<br>salt lake city, ut 84103<br><a href="tel:801-550-5815" value="+18015505815" target="_blank">801-550-5815</a><br>
<a href="http://oegeo.wordpress.com" target="_blank">http://oegeo.wordpress.com</a><br>
</div></div></div><br><br clear="all"><br>-- <br>martijn van exel<br>geospatial omnivore<br>1109 1st ave #2<br>salt lake city, ut 84103<br>801-550-5815<br><a href="http://oegeo.wordpress.com" target="_blank">http://oegeo.wordpress.com</a><br>