the BitSetIdTracker must be enhanced anyway to support 64 bit.
i guess we have to split the /BitSet positiveSet/ into lower and upper sets,
right? And remove the LongAsInt class and other long to int and vice versa
conversions.
martin
___
Good idea,
A couple of values that gave incorrect results:
Mo-Fr 08:62-27:88
Mo-Fr 09:00-16:00; Su 11-12
mo-we 12:00-15:00; Su off
24/7
we 09:00-12:00,13:30-15:00
The first is obviously incorrect so should produce an error rather than
attempting to parse it.
In the second and third example,
Hi,
is there a tool already existing that can simplify ways in an .osm file?
What I'm looking for is something that removes all intermediate nodes from a
way, as long as they are not used in another way.
Example:
way id=1
nd ref=1/
nd ref=2/
nd ref=3/
nd
Hello Maarten!
Josm's Simplify area plugin should do something similar to what you are
seeking, given correct settings.
On May 5, 2013 7:58 PM, Maarten Deen md...@xs4all.nl wrote:
Hi,
is there a tool already existing that can simplify ways in an .osm file?
What I'm looking for is something
Hi,
have a look at
http://lists.openstreetmap.org/pipermail/dev/2012-May/024947.html
https://github.com/podolsir/osmosis-simplifyways
If you do not have negative IDs in your dataset, the last link should work.
Regards,
Christian
Am 05.05.2013 14:56, schrieb Maarten Deen:
Hi,
is there a
On 2013-05-05 15:38, Christian Müller wrote:
Hi,
have a look at
http://lists.openstreetmap.org/pipermail/dev/2012-May/024947.html
https://github.com/podolsir/osmosis-simplifyways
That doesn't want to work for me. I have the latest germany file and
when I run that (with enableDateParsing set
Hi,
maybe talk to user Netzwolf, who developed already a very extended
parser for opening_hours.
See http://www.netzwolf.info/en/cartography/osm/time_domain/form_hours
Henning
Am 04.05.2013 17:06, schrieb Ian Dees:
In an effort to bring opening_hours editing to iD and to make it easier
for
Hello!
Is there any style guide for coding?
The wiki page
https://josm.openstreetmap.de/wiki/DevelopersGuide/StyleGuide
only refers to the Oracle Javadoc style guide and not to the Oracle Code
Conventions for Java.
The reason why I am asking is, that I came along a big number of case where
On Sat, 4 May 2013, Nzara wrote:
1) Have a requirements section:
Requirements
* JDK 1.6 (higer versions may do also)
Today 1.7 should be requested, although 1.6 still works.
* ant - for the build process
* svn command line - for the build process
* (optional) an IDE of your choice, e.g.
On Sun, 5 May 2013, Tobias Hirning wrote:
Is there any style guide for coding?
It's in the wiki:
* make sure there is no trailing white space
* don't use multiple consecutive empty lines
* JOSM uses 4 characters indentation and no tab stops
* Document your code thoroughly. Many people
10 matches
Mail list logo
