-
Notifications
You must be signed in to change notification settings - Fork 4
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
Restrict PointsType to a well defined format #80
Comments
The most common form of PointsType, as well as the one in all of the examples, seems to be of the
It might also be advantageous to split |
I propose following - a bit more complex, but looks it works (should handle numbers as integer or floating point expressed as 2.4 or .5 or 1.832e-5 or 1.322E-5 or 3.4e+3 or 2.3E+3 or 2.4E5 or 8.9e2, comma separated inside a pair, or space separated inside a pair and at least two pairs - this is useful for basic baseline, not for poly shape). This would match with what we stated into version 4.4 (\d?\d*(.\d+([eE][-+]?\d+)?)?\s*[,\s]\s*\d?\d*(.\d+([eE][-+]?\d+)?)?\s+)+\d?\d*(.\d+([eE][-+]?\d+)?)?\s*[,\s]\s*\d?\d*(.\d+([eE][-+]?\d+)?)? |
This topic is derived from #49. On previous issue we focus on changing documentation and announce PointsType restrictions, and on this topic we will have the discussion regarding restrictions implementation, for version 5.0
The text was updated successfully, but these errors were encountered: