Closed patricknee closed 7 years ago
I know what this is, when there is a classification range, I create all permutations within the number range. This does two things: 1) not all permutations are actual defined classifications, even though it aids searching 2) large ranges.
I should probably limit the range to something small. And in the future come up with a better way of handling ranges. And actual lookup would be beneficial but right now I am limiting it to what is in the document.
Looking at the number range above, I should be better handling the range.
The code which matches and expands the range is here: gov.uspto.patent.model.classification.UspcClassification lines 233-258
I will further look into this.
I have checked in code which will throw an ParseException for any Range over 99.
OK, I will do a pull and run through my spot test of the Hits of the 80s, 90s, 00s, and 10s.
This appears resolved.
After being written into an individual json file by TransformerCli this file is 42mb (other files are ~100k). It is filled with this following section of the json file (trimmed).
The google copy of the patent looks "normal" without this type of data. Is this an error?
Year: 2010 file: ipg100105.zip US7640662B2.json
....trimmed....