You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: jongleur1983 [Submitted to the original trac issue database at 3.08pm, Monday, 16th August 2010]
Osmarender takes a lot of time calculating centers of areas.
There repeatingly messages like the following are posted to the console:
areaCenter: 8.748932431116977,51.7043812036579
I would like to have the ID of the area added here. The information about the calculated center is useless unless the user does not debug at current, while the ID of the area could help estimating the progress by checking the position of the area in the .osm-file
The text was updated successfully, but these errors were encountered:
Reporter: jongleur1983
[Submitted to the original trac issue database at 3.08pm, Monday, 16th August 2010]
Osmarender takes a lot of time calculating centers of areas.
There repeatingly messages like the following are posted to the console:
areaCenter: 8.748932431116977,51.7043812036579
I would like to have the ID of the area added here. The information about the calculated center is useless unless the user does not debug at current, while the ID of the area could help estimating the progress by checking the position of the area in the .osm-file
The text was updated successfully, but these errors were encountered: