Tag Info

New answers tagged

0

We provide a free OSM converter, which you can use to import OSM data into our routing solutions. Could be either RW NetServer 3 (standalone server application) or RW Net 4 (.NET component). Both can be seen on www.routeware.dk and provides standard features such as routing, driving directions, travelling salesman optimization etc.


0

I seemed to have solved the problem by taking this approach: 1) perform create table highwaysinglegeom as select st_union(the_geom) from analysis.po_highway 2) perform the update query above using the single geometry highway table as the intersection layer rather than separate multilinestrings from my network.


0

pgRouting is another routing option using OpenStreetMap data. pgRouting.org pgRouting extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality. Core Features pgRouting provides functions for: All Pairs Shortest Path, Johnson’s Algorithm All Pairs Shortest Path, Floyd-Warshall Algorithm Shortest Path ...


2

GraphHopper (using OpenStreetMap Data) GraphHopper offers memory efficient algorithms in Java for routing on graphs. E.g. Dijkstra and A* but also optimized road routing algorithms like Contraction Hierarchies. It stands under the Apache License and is build on a large test suite. OpenStreetMap is directly supported from GraphHopper. Without ...


0

Looks like you need something like Osmosis or imposm. These are tools that will convert raw OSM data output by JOSM into a custom postgis format. Because OSM is free-tagging, there is no "official" way to convert the XML into a usable data structure that a GIS can read. The main importers currently focus on roads, buildings, points of interest etc. because ...


0

Vivek, one issue you will have is for very long ways. Returning the OSMid for a long way will inhibit that whole way being used, rather than a possible simple route around the problem area. If your area is not huge, (city size) you may want to consider PG_Routing as you can dynamically update the routing tables for an individual segment based on a lat long ...


2

What you are looking for is called 'reverse geocoding' and is implemented e.g. with Nominatim API


0

There is likely a problem with your SQL in the subquery... If you are putting this query as the subquery EXACTLY... SELECT * FROM shortest_path_astar(' SELECT gid as id, source::integer, target::integer, length(the_geom)::double precision as cost, x1, y1, x2, y2 ...



Top 50 recent answers are included