Skip to content
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

try to document use_nodecache.py #255

Merged
merged 1 commit into from
Jun 18, 2024
Merged

Conversation

matkoniecz
Copy link
Contributor

@matkoniecz matkoniecz commented Jun 18, 2024

note that I am pretty sure it is correct but not fully sure

And I do not understand yet how can I use nodecache for areas and is it even doable/useful with multipolygons

I am also lacking clarity whether way should be understand as "OSM way object" or "linear way which excludes OSM closed ways representing areas".

Will try to experiment and also add this info in future.

@lonvia lonvia merged commit 068e5e3 into osmcode:master Jun 18, 2024
21 checks passed
@lonvia
Copy link
Member

lonvia commented Jun 18, 2024

I am also lacking clarity whether way should be understand as "OSM way object" or "linear way which excludes OSM closed ways representing areas".

OSM ways. When you add an area handler, then closed ways will be presented twice, once in the way handler as a linear feature and again in the area handler as a polygon. There is no guarantee as to which comes first. Consulte the libosmium manual for details.

As said before, better documentation is in progress.

@matkoniecz matkoniecz deleted the patch-2 branch June 18, 2024 12:32
@matkoniecz
Copy link
Contributor Author

As said before, better documentation is in progress.

And I will definitely use it when it will appear! Though for now I (mostly) manage to use what is now, so unless it will appear really soon it seems that waiting is not needed.

Unless it refers to that it is pointless to submit improvements now as new version will replace and obliterate all existing content anyway?

@lonvia
Copy link
Member

lonvia commented Jun 18, 2024

Unless it refers to that it is pointless to submit improvements now as new version will replace and obliterate all existing content anyway?

There is a high probability that this will happen for any documentation changes. I haven't made up my mind yet, what will happen to the examples.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants