|
|
Posted by Steve on 11/06/06 17:18
| I was looking to keep it pretty simple
|
| mfg, year, engine, drive train, # doors
|
| I gave you a link to the vin patterns for chevy and some others from
| another site, if this was any help.
|
| http://www.decodethis.com/patterns.aspx <-- this is a good source of vin
| patterns
|
| oh well as zim would put it
|
| doom doom.....
not so dooming. you can use that site to put into the code samples i created
and you'll have all the flexibility to decode vins as that site does. the
problem is, that site covers archived years/makes/models and doesn't
accurately describe newer vehicles.
the classes i included simply lay out a set of regular expressions as the
key to an array of values - whether the values are body type, series, model,
etc.. each expression is executed on the vin until a match is found. when
found, the value of that array element is returned. it's pretty flexible but
may get lengthy. keeping each manufacturer seperate (it's own class), helps
lower the processing overhead while still maintaining a uniform interface.
have you investigated the possibility of speaking directly with a couple of
manufacturers to see if they'd provide you with a data file of their vin
translation data? i got most of my info straight off the web (through a
BUNCH of searches). anyway, i'm sure most would be willing to help at least
in some way.
Navigation:
[Reply to this message]
|