Goldtex Apartments (315–23 N 12th St)

A property-specific extension of the Philadelphia L&I Open Data Navigation Guide. All facts in this file were verified against the Eclipse ArcGIS feeds and the Carto open-data mirror on May 14, 2026. Field names and endpoint URLs are reproduced verbatim from working queries.

If anything in this file fails to reproduce, the data systems have changed. Re-verify and update.

See also: Main report · Site overview

1. Canonical property identifiers

Use these exact values when constructing queries. Variants will return zero rows.

Address-resolution traps

• The block has 315-23 N 12TH ST (Goldtex) and 325-27 N 12TH ST (Wang Sheng LLC, separate building). There is no 315-25.
• Queries against '315 N 12TH ST', '315 N 12th Street', or '315-25 N 12TH ST' return zero rows. The official string is exactly 315-23 N 12TH ST (hyphen, no commas, uppercase ST).
• Prefer opa_account_num = '881519440' over address-string matching for every L&I query. OPA is the stable join key. Address strings are inconsistent across tables and pages.

2. Authoritative query endpoints

Per the navigation guide §1, Eclipse is authoritative for current state and Carto is authoritative only for bulk historical aggregation and 311 complaints. The Eclipse Property History page at li.phila.gov/property-history/… is a Vue SPA that does not return data to a plain HTTP fetch — it dispatches to the ArcGIS feature services below. Query those directly; that is what the page itself uses.

Base host: https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/

All ArcGIS REST queries accept where=<sql>, outFields=*, f=json, resultRecordCount=<n>, resultOffset=<n>. Default page size is ~1000 records; if the response includes "exceededTransferLimit": true, paginate.

3. VIOLATIONS schema (Eclipse field list)

objectid                 posse_jobid              addressobjectid
parcel_id_num            casenumber               casecreateddate
casecompleteddate        council_district         casetype
casestatus               caseresponsibility       caseprioritydesc
violationnumber          violationdate            violationcode
violationcodetitle       violationstatus          violationresolutiondate
violationresolutioncode  mostrecentinvestigation  publicnov
opa_account_num          address                  unit_type
unit_num                 zip                      censustract
opa_owner                systemofrecord           geocode_x
geocode_y                underappeal

Date fields (casecreateddate, casecompleteddate, violationdate, violationresolutiondate, mostrecentinvestigation) are returned as Unix epoch milliseconds. Convert before display.

underappeal is Y or N. Cross-reference an underappeal = 'Y' record against the APPEALS layer.

4. Status semantics

Two status fields exist. They are not redundant.

casestatus (case-level)

• IN VIOLATION — at least one violation on this case is unresolved.
• CLOSED — case has been closed. Inspect individual violationstatus values to learn how it closed.

violationstatus (individual-violation level)

This is the field that distinguishes real compliance from administrative closure:

• OPEN — currently unresolved. This is the only value that means “open.”
• COMPLIED — actual confirmed compliance.
• CLOSED — administratively closed without a recorded compliance event. Not real compliance.
• CLOSEDCASE — administrative closure of the parent case. Compliance not confirmed.
• RESOLVE — resolved via appeal or other path. Compliance not confirmed.
• ERROR — data-entry anomaly. Not a clean closure.

5. Known-truth anchors as of May 14, 2026

If a fresh query disagrees with the values below, either the data has changed or the query is wrong. Re-verify before propagating.

Active cases — 6 cases, 16 violations

6. Working queries

All queries below were executed successfully against live endpoints on May 14, 2026. Substitute the OPA account number to retarget.

6.1 Open violations only — Eclipse direct (authoritative)

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/VIOLATIONS/FeatureServer/0/query?where=opa_account_num%3D%27881519440%27+AND+violationstatus%3D%27OPEN%27&outFields=*&f=json

Expected: 16 features as of 2026-05-14.

6.2 Full violation history — Eclipse direct

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/VIOLATIONS/FeatureServer/0/query?where=opa_account_num%3D%27881519440%27&outFields=*&f=json&resultRecordCount=2000

Expected: 124 features as of 2026-05-14.

6.3 Carto cross-check (mirror; not authoritative for current state)

https://phl.carto.com/api/v2/sql?q=SELECT+*+FROM+violations+WHERE+opa_account_num+%3D+%27881519440%27&format=json

Use this only to confirm parity for historical records, never for current status. The Carto mirror can lag Eclipse.

6.4 Rental license — Eclipse direct

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/BUSINESS_LICENSES/FeatureServer/0/query?where=opa_account_num%3D%27881519440%27&outFields=*&f=json

Expected: rental license #602204 with status reflecting the Feb 28, 2026 expiration. If Carto’s mirror displays this license as Active, Eclipse is authoritative — the license is expired.

6.5 Permits

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/PERMITS/FeatureServer/0/query?where=opa_account_num%3D%27881519440%27&outFields=*&f=json&resultRecordCount=2000

6.6 Appeals

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/APPEALS/FeatureServer/0/query?where=opa_account_num%3D%27881519440%27&outFields=*&f=json

6.7 Case investigations (inspection events)

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/CASE_INVESTIGATIONS/FeatureServer/0/query?where=opa_account_num%3D%27881519440%27&outFields=*&f=json&resultRecordCount=2000

6.8 311 complaints — Carto only (Eclipse does not expose these)

https://phl.carto.com/api/v2/sql?q=SELECT+requested_datetime%2C+service_name%2C+status%2C+description%2C+address+FROM+public_cases_fc+WHERE+upper(address)+LIKE+%27%25315-23+N+12TH%25%27+OR+upper(address)+LIKE+%27%25315+N+12TH%25%27+ORDER+BY+requested_datetime+DESC&format=json

Address-string match is required here because public_cases_fc does not carry opa_account_num for every record. Vary the LIKE pattern as needed.

6.9 OPA ownership and assessment

https://services.arcgis.com/fLeGjb7u4uXqeF9q/ArcGIS/rest/services/opa_properties_public_pde/FeatureServer/0/query?where=parcel_number%3D%27881519440%27&outFields=*&f=json

The OPA layer uses its own field naming (parcel_number, not opa_account_num). Confirm the field list from /FeatureServer/0?f=json before composing variants.

7. What is NOT retrievable from public data

Document these absences explicitly; do not let them pass without comment.

• Inspector identity. No name, badge number, or unit appears in any layer. FOIA only.
• Inspector notes and photos. FOIA only.
• Internal L&I, PPD, or counsel correspondence. FOIA only.
• Tenant identity on 311 complaints. Anonymized in the public export. FOIA only.
• Whether a physical re-inspection actually occurred. COMPLIED is a recorded status; it is not by itself evidence of a site visit.

The L&I Open Records Officer handles RTKL requests under 65 P.S. § 67.101 et seq. Standard response window: 5 business days, extendable to 30. Denials appealable to the Office of Open Records.

8. Cross-reference protocol for any Goldtex claim

Before propagating a numeric or status claim about Goldtex (open-violation count, license status, ownership, 311 volume), execute these steps anchored to OPA 881519440:

1. Eclipse VIOLATIONS by OPA → current open count (§6.1).
2. Eclipse BUSINESS_LICENSES by OPA → current license status (§6.4).
3. Carto public_cases_fc by address → 311 history (§6.8).
4. OPA layer by parcel → ownership confirmation (§6.9).
5. Compare against the anchor values in §5 above. If anything diverges, the systems have updated; refresh the anchors and note the date of the new pull.

Always record the date and time of the pull. Never report a Carto status field as current state without an Eclipse confirmation.

Last verified against live Eclipse and Carto feeds: May 14, 2026. Maintained at jlegal.pro/agents_goldtex.html.
Companion to Navigating Philadelphia L&I Open Data.

Read on Medium • justin@jlegal.pro • Text: (908) 379-1102

← Back to Horn / Goldtex Consolidated Report

Do not contact, threaten, harass, or interfere with any person named or referenced on this site. This record is published for documentation, transparency, and lawful review only.