Arizona dust?
Dave
look at the original parking data. There is a field Rotation which is integer. That is ok so long as the rotation is to the nearest whole degree.
That value of the field can be edited from 0 to 20, 30, 40, 12 etc one by one in the data table.
There are parallel parking spaces in real life.
Mapimport the data to dwg objects and by selecting all the parking spaces to be at 20 degrees, it allows typing 20 once in the properties palette in the Rotation field.
by using adedefdata command I added Rotation1 field into the data and set the type to real. That allows decimal degrees for rotation. Same process, select a group of parking spaces points and set the property to say 223.36. This has to do with how picky you have to be with the map. Most people would not miss the decimal portion but if you have a GPS guided paving machine it may be embarassing in the end.
Now mapexport all the points and data to a new shp or other data type(sdf, etc)
put that shp into the map and style the points with a square and reset width and height to the size of the parking space.
Drop down the rotation list and select use expression, select property Rotation, OK, Apply and close
(see 4ParkingStyle.tif)
Now the parking points are aligned to the rotation as asked for.
All of the data work which can be avoided by putting the rotation value into the data as the data is collected.
As an aside, One point or two points per set of parking spaces and use an array dynamically to draw rectangles rotated to position, explode the arrays and mapexport to closed polygons. saves field time, especially if you have an offset laser and gives a nice result also.
BTW the photos can be found here https://tnris.org/data-download/#!/statewide
and data for the buildings, streets, and other city data here http://gis.dallascityhall.com/homepage/shapezip.htm
Dave P