pbf2json | OpenStreetMap pbf parser which exports json | JSON Processing library

by pelias Go Version: 6.10.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | pbf2json Summary

pbf2json is a Go library typically used in Utilities, JSON Processing, Nodejs applications. pbf2json has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

pbf2json creates a JSON stream of openstreetmap data from any PBF extract, you can pick-and-choose only the bits of the file you want, the library will take care of de-normalizing the relational data (nodes/ways/relations) so you can put it straight in to your favourite document-store, inverted index or graph database.

Support

Quality

Security

License

Reuse

Support

pbf2json has a low active ecosystem.

It has 126 star(s) with 34 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 22 have been closed. On average issues are closed in 40 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pbf2json is 6.10.0

Quality

pbf2json has 0 bugs and 0 code smells.

Security

pbf2json has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

pbf2json code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

pbf2json is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

pbf2json releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 911 lines of code, 57 functions and 15 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed pbf2json and discovered the below as its top functions. This is intended to give you an instant insight into pbf2json implemented functionality, and help decide if they suit your requirements.

print writes the decoder to leveldb .
Main entry point
index is the main entry point for decoding .
computeCentroidAndBounds computes the centroids for the given latlons .
simplify simplifies the points in the polygon
Parse settings from leveldb
indexRelationMembers indexes the relation members .
selectEntrance picks the first entry from the list of entries .
nodeToBytes converts an osmpf . Node to a byte slice
bytesToLatLon converts a byte slice to a map

Get all kandi verified functions for this library.

pbf2json Key Features

No Key Features are available at this moment for pbf2json.

pbf2json Examples and Code Snippets

No Code Snippets are available at this moment for pbf2json.

Community Discussions

Trending Discussions on pbf2json

OpenStreetMap osm.pbf file, number of paths in federal states compared to the number of paths in a country

QUESTION

OpenStreetMap osm.pbf file, number of paths in federal states compared to the number of paths in a country

Asked 2020-Jan-03 at 08:25

I would like to develop a small geocoder using OpenStreetMap. Now I downloaded the file germany-latest.osm.pbf and converted it with the tool pbf2json into a JSON stream. With this tool it is now possible to "pick" only JSON's with the planet type way. These contain the respective street, city, house number, postal code and the position, so everything I need for the geocoding.

But what I don't understand is that the file saarland-latest.osm.pbf which has the state Saarland (the smallest state in Germany) has about 658548 ways and the file germany-latest.osm.pbf has about 3792000 ways. Is there something wrong with the parser, or does "germany-latest.osm.pbf" only contain the "most important" roads in Germany, while the osm.pbf files of the different federal states contain all roads within the federal states?

So I have to download each state individually to get all streets of the whole country?

...

ANSWER

Answered 2019-Dec-29 at 11:29

The .osm.pbf files from Geofabrik are complete extracts, you do not need the files for individual states in addition to the country extract.

I can confirm your count of the number of ways in the Saarland file. However, I count 50566293 ways in "germany-latest.osm.pbf" when parsing it with a relatively low-level library (osm4j).

So presumably, the issue is somewhere in your pipeline. Is it possible that the difference results from filtering based on the presence of certain tags, e.g. address information?

Source https://stackoverflow.com/questions/59509998

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pbf2json

You can download it from GitHub.

Support

If you are doing a release and would like to compile for all supported architectures:. note if this is your first time doing this please read the notes in './compile.sh' to set it all up on your machine.

Find more information at: