Thanks, Adam,
That should get me the last bit of the way.
Martha
On Wednesday, October 2, 2019 at 4:49:01 PM UTC-7, Adam Lodge wrote:
>
> Martha,
>
> I wish I could help with understanding why json export is working and csv
> isn’t. Unfortunately, I can’t. That said, toward working with you
Alexi,
I'll enter it with ¦ (Alt+0166) just to be sure, but I thought I was on
track. Won't hurt to try again.
Thanks,
Martha
On Wednesday, October 2, 2019 at 5:54:27 PM UTC-7, Alexei Peters wrote:
>
> Hi Martha,
> I think you're looking for the wrong character. In your initial post the
> s
Hi Martha,
I think you're looking for the wrong character. In your initial post the
stack trace indicated the "broken bar" character.
see http://www.fileformat.info/info/unicode/char/a6/index.htm
Try searching for that character instead.
Cheers,
Alexei
Director of Web Development - Farallon Geo
Martha,
I wish I could help with understanding why json export is working and csv
isn’t. Unfortunately, I can’t. That said, toward working with your json
output, you can identify the uuid of nodes/fields that store geometry with this
sql:
select
b.name as model_name,
a.name as n
One more bit of information: I was able to export the business data to
json. Naturally, I did not find '|' in the resulting file.
If this export includes geographies (or lack thereof, which is what I'm
really after) for this resource model, I might be able to query what I need
based on the too
Alas, Gentlemen, neither effort returned anything. In PGADMIN4, I ran both
of the following with no results returned:
SELECT
a.resourceinstanceid,
b.name as card_name
FROM tiles a
JOIN cards b on a.nodegroupid = b.nodegroupid
WHERE 1=1
and tiledata::text like '%|%'
set standard_conformi
Thank you,to both Adams.
I will run both suggestions. Both are helpful to my ongoing database
activities. The more approaches in my toolbox, the better.
It is great to know that the cards can be treated as flat files with
tiledata; I missed that somehow. Iterating through each record with the O
