mjreno

@mwtoews @aleaf Apologies for not following up on this suggestion earlier. I also like the idea and in keeping with the thought that this parameter would be transparent to MODFLOW...

@mwtoews I was thinking something similar- a file analogous to the usgs.model.reference files. Here's an example: ``` xul 1954815.00 # x-coordinate of the upper left of the model grid yul...

Getting the new parameter into the package isn't a big deal but updating the binary format will break other applications that directly parse the version 1 format. A sidecar file...

I think that would limit the types of user inputs that would be supported but is probably a good compromise for a first step. I'd be interested to hear from...

If it sounds reasonable then I'm thinking to add a ```DIS CRS``` parameter and a new ```FILEOUT``` option for the projection file. If ```CRS``` is provided with the ```prj FILEOUT```...

I can see it both ways. I agree that these are import considerations but I'm not sure that MODFLOW 6 is the right context to promote or regulate best practices...

That's an interesting thought @aleaf. Would the file always contain a single line of text with a prescribed maximum length, i.e. 100? Do you see distinct workflow use cases for...

I had a similar thought @mwtoews - splitting up long strings into either the comment or dedicated text fields. @aleaf is this a general enough solution if one way or...

@mwtoews @aleaf feel free to review or comment on the current solution in the PR's above. I'm thinking to merge this soon and then the basic capability would be available...