This will show it without a data source MAP Extent 0 0 50 50 Units Meters Size 100 100 OUTPUTFORMAT NAME GIF DRIVER 'GD/GIF' MIMETYPE 'image/gif' EXTENSION 'gif' END SYMBOL Name 'circle' Type Ellipse Points 1 1 End Filled True END LAYER Status Default Type Line Name 'Test1' FEATURE Points 45 0 50 50 End END # Feature FEATURE Points 0 45 5 0 End END # Feature CLASS Symbol 'circle' Size 10 Color 255 0 0 OverlaySymbol 'circle' OverlaySize 8 OverlayColor 0 0 0 END # Class END # Layer END # Map
Greg Stephen Woodbridge wrote: > > rich.fromm wrote: >> Steve Lime wrote: >>> Can you post your mapfile and a small data sample? >>> >> >> The map files are in the posting starting this thread: >> http://www.nabble.com/wide-lines-not-complete-at-the-edges-to14609249.html >> >> My data is a large dataset from navteq that I have imported into postgis. >> I'll have to look into both what would be needed to do to trim it down, >> and >> whether or not my license allows me to redistribute it at all (I'm >> guessing >> not). Although I probably could generate a test case with synthetic >> data, >> although that would require me researching a little bit about how the low >> level data is stored. >> > > Rich, > > Based on looking at you images, I would just create a simple table in > postgis and put in a few lines in a 0,0,5,5 space and create a simple > one layer mapfile to display that on a simple 500x500 image. Using > number like this make the math trivial. you can then pgsql2shp dump the > table as a shapefile, and change you DATA statement and zip the mess up > and attach it to a bug. > > Let me know is you need some more specific instructions or get stuck on > doing this. This looks like a bug that need to get fixed. > > -Steve W > > -- View this message in context: http://www.nabble.com/wide-lines-not-complete-at-the-edges-tp14609249p14678938.html Sent from the Mapserver - User mailing list archive at Nabble.com.