-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting proper plotmap aspect ratio #12
Comments
I agree that this is a missing component here! The corners of maps bouding box are stored in the This is the code for the Reno map that comes with OpenStreetMapX
Since the
Hence the size of the If you want to do a PR helping with this functionality it will be very welcome. |
Thanks. I'll add this code this afternoon. I've just created a new function plot_nodes_as_symbols! that is similar to plot_nodes!, but allows arbitrary symbol strings to be plotted at node locations instead of numbers. You'll see that code shortly. |
Sounds great! should you need any support/instructions do not hesitate to ask. |
I just cloned and then committed my changes to the Master. Is this right? I'm a novice at GitHub. |
I see that I need to create a fork first. Just did that. Will now try to commit. |
Do you see my changes? if not, what do I need to do? |
I accidentally created two pull requests. The second one contains the changes of the first. Sorry about that. |
When I load an OSM file and issue the plotmap command without height and width arguments, the aspect ratio is automatically set as 1:1, namely, 600 x 600. I feel that the default behavior should be that a meter in the horizontal axis is the same scale as a meter on the vertical axis. I've played around with how to extract the OSM bounding box in meters, but have failed. Can someone provide some hints? I'd like to update plotmap to do this. I would also add the behavior that if only one of the height and width arguments is provided, then the other dimension would be automatically chosen to preserve the aspect ratio.
The text was updated successfully, but these errors were encountered: