New answers tagged

1

Start with the demo.bat/sh and modify the params to use your source You'll get two results, the gph and an sql. The sql lets you proceed with PostGIS,pgRouting,QGIS For deeper dives (native .gph) follow the Java-Example on the WebSite. Or use osm2po's simple REST-API which handles most common cases. It is documented on the site as well. The documentation ...


0

Or perhaps it is because you are transforming your ways to srid=4326 (WGS 84) to compare against your linestring with an srid=900913 (Deprecated Mercator)? ST_Transform( marks.way, 4326 ) st_setsrid( ST_GeomFromText('LINESTRING(121.1527761 13.9413653,121.154058 13.9413113,121.1550161 13.9412372,121.1559079 ...


0

Try analyzing your sub-statements to find out why it isn't working. I had a compound select statement such as yours which worked on one set of data but didn't on another due to the statement referring to the record id rather than a target or source id. Doing so, you may discover that you are referencing/comparing the wrong geometry srid. From your ...


0

I followed this guide to ensure that my osm2po data was properly/fully indexed. There were no indexes on the Geometry columns after a fresh load of data. Most of my undesired performance issues were related to the Tiger Geocoder taking ~13 secs to provide a result after a fresh load of tiger data with 8 states. I followed this guide for missing indexes ...


1

You should use ST_DWithin as a filter on your location as below SELECT pubs.name FROM pubs WHERE ST_DWithin([Your Location in units of projection], pubs.the_geom, [Distance in units of the projection used]); the_geom is the geometry column of your pubs table. If your location data is in GeoJSON format (You could maybe clarify this in your question) you ...


3

Use this guide to set up indexes for a spatial database. Here is the gist of it: 1. create indexes on ID, source and target columns. 2. create index using GIST on geom column. 3. vacuum 4. cluster on geom column 5. analyze for my _4pgr and _vertex tables, only the source and target columns had indexes after the import (osm2po-core-5.1.0).


0

The result you provided was likely generated by a similar command (windows) which has the -q option: C:\>psql -U postgres -d postgres -q -f na_2po_polyrel.sql You can remove the -q option and it will output each command from the file to the screen, however, doing so will not output any kind of "successful" message but you could follow it to determine ...


0

osm2po is compatible with (and build for) Java 1.6. I think you'll have to use the compiler option -target 1.6 in order to be binary compatible. The original doc says: The major version number will be ..., 50 for Java 6, and 51 for Java 7. Tip! Read this to make things easier: How to extend OSM2PO with ferry durations?


0

This line causes the output to be directed to the screen postp.pipeOut = true please see this link for more information.


0

Check your osm2po config file to ensure you create the desired routing table. See this post



Top 50 recent answers are included