This is the first time I've tried using the DbGeography type in my EF Code First design. My question is: Should I use simple float fields to store the longitude and latitude of the location, or should I use geometry like SQL?
I'm starting to think that geography makes things more complicated than they should be. I will do area calculations based on long / lat.
source
share