Format error when the Longitude or Latitude is small such as : 0.000007589 #5
Open
gzqlovemxq wants to merge 138 commits into
Open
Format error when the Longitude or Latitude is small such as : 0.000007589 #5gzqlovemxq wants to merge 138 commits into
gzqlovemxq wants to merge 138 commits into
Conversation
Conflicts: ogr2osm.py translations/uvmtrans.py
…manipulation of the layers. This can be disabled with the new flag --no-memory copy. Benchmarking indicates no significant speed difference between the options.
… tag even though all relations generated are MPs
By default use 1 nanodegree. The OSM API uses 100 nanodegrees
By default any points which will be considered as the same by the OSM API are considered the same for merging.
Corrected python-gdal install instructions.
Create setuputils script for PyPl distribution.
Add arguments for JOSM's upload=never, download=never, and locked=true options
Fix axis swapping with GDAL 3.0
option --add-timestamp causing error:
Traceback (most recent call last):
File "/home/andrzej/PycharmProjects/offline_riskzones/venv/bin/ogr2osm", line 11, in <module>
load_entry_point('ogr2osm', 'console_scripts', 'ogr2osm')()
File "/home/andrzej/PycharmProjects/offline_riskzones/venv/src/ogr2osm/ogr2osm.py", line 781, in main
output()
File "/home/andrzej/PycharmProjects/offline_riskzones/venv/src/ogr2osm/ogr2osm.py", line 505, in output
attributes.update({'timestamp':datetime.utcnow().strftime('%Y-%m-%dT%H:%M:%SZ')})
NameError: name 'datetime' is not defined
"wb" is expecting b"" while 1 line lower there is casting to string
fixed bugs for --saveID and --add-timestamp
Seeking a new maintainer banner in README.md
add a LICENSE file containing the MIT license text, as is necessary
Add CI tests from pnorman's master branch
Improve performance by eliminating mergePoints
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the Longitude or Latitude is small such as: 0.000007589, the output will be like 7.589e-6, and it will also be stored as 7.589e-6 in the osm file, which will result in the coordinate errors.